MainFrame sFTP issue

Hi Experts,

We have issue in waking up the files in MainFrame. When files are awake this works exacly fine. In MainFrame server when the file goes to sleep mode, this command fails. When issuing command how to wake the file and get it? Please help ASAP.
get get //'temp.OLD(0)' temp

Open in new window

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

What do you mean by the files are asleep and awake?  I have never heard of those terms in relationship to files, nor have I heard of them in relationship to z/OS.

victory_inAuthor Commented:
Since the files are too many they will go in sleep mode to save some memory itseems in MainFrame. I'm not a MainFrame person. Then if you need them u need to wake them up and get them. But my question is there a way to wake them up and get the file from MainFrame to Linux. This is the MainFrame issue files are going into sleep mode. When I issue sFtp COMMAND FROM unix TO MainFrame, it is throwing me an error """file is not located"""" though there is a file, but in sleep mode. How to wake them up and get it into Linux from MainFrame by using SFTP?

I have never heard of this "sleep" mode on z/OS before and I have done some searching and I have not found anything even coming close to this.

Were did you get this information from?  Can you point me to some doc?
victory_inAuthor Commented:

in general, if no one acces the file for 3 or 4 days, it goes to sleep. To wake them up you need to issue the following command.
Ah, they get migrated.  On z/OS in order to save disk space if a file has not been access in "x" amount of time, the system will "move" it to either level 1 or level 2 migration status.

Level 1 is still on disk, but compressed in a special file format.  Level 2 is on tape.

Typically the file will automatically be recalled if you try to access it, but if it is migrated to level 2 (tape) it may take awhile, Any where from a few minutes to hours depending on how many tape drives are available and how many tasks are using tape or waiting to use tape.

There is nothing you can do, except to detect that the file is migrated and issue the HRECALL command for it and then check back again later.

Again, the system should automatically issue the recall if you attempt to access the file, it just may take it awhile before it can get the file recalled.

If you do sftp and do a ls against the file, what does it show?  I would test, but I have IBM's sftp server and it does not support accessing "mvs" files, it only supports hfs based files and indvidual hfs files don't get migrated.

If may show that it is "Migrated", in which case if your sftp client supports it you could issue the hrecall command.

Your z/OS people need to look into this.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.