MVSFORUMS.com

arvibala · Beginner Joined: 12 Feb 2008 Posts: 142 Topics: 67

I have a Job that runs once is a month. I receive a file from Oracle Server into Mainframe, say HLQ1.MLQ1.MLQ2.ARVIND. The Monthly Job processes this file and empties it. The request is they want us to have this file catalogued so that they populate data thru FTP. The problem is since this is a Monthly process, when they FTP the data onto this file, this file goes into MIGRAT2 and their FTP fails. How to Catalog a file so that it doesnt goes into MIGRAT2 mode?
_________________
Arvind
"You can make a difference with your smile. Have that with you always"

taltyman · Posted: Mon Dec 29, 2008 9:19 pm Post subject:

FTP can be set to automount to allow a recall. See who is the systems programmer for FTP at your site.

expat · Posted: Tue Dec 30, 2008 2:59 am Post subject:

You can not catalog a file in any different way to avoid space management.

Assuming that your site has DFSMSsms implemented, you need to speak to your storage management team to provide a different MGMTCLAS for this dataset so that it does not get migrated.
_________________
If it's true that we are here to help others,
then what exactly are the others here for ?

arvibala · Beginner Joined: 12 Feb 2008 Posts: 142 Topics: 67

Thanks All
_________________
Arvind
"You can make a difference with your smile. Have that with you always"

kolusu · Posted: Tue Dec 30, 2008 2:29 pm Post subject:

arvibala,

Code a HRECALL STEP with WAIT as the first step in your JCL.

expat · Posted: Wed Dec 31, 2008 2:55 am Post subject:

Kolusu, although your suggestion is widely used, it is sometimes frowned upon when large files are involved.

On one occurence, the requested HRECALL was queued behind almost 900 other requests and waited for over three hours before the recall step completed. This kept an initiator occupied for all of that time at month end.

Although this was probably a once off event, I believe that it is a far better practice to speak to the storage group and manage the dataset correctly in the first place, rather than have it constantly jigging up and down between tape and DASD.

Just the humble opinion of a storage guy Very Happy

_________________
If it's true that we are here to help others,
then what exactly are the others here for ?

jsharon1248 · Posted: Wed Dec 31, 2008 8:45 am Post subject:

Ravi · Beginner Joined: 27 Jun 2005 Posts: 88 Topics: 2

Make HLQ1.MLQ1.MLQ2.ARVIND as a GDGBase and then start using the current version. In that way, you are backing up on whatz being FTP'ed too. If a MF job is doing the pull, then you need to allocate the file prior to the FTP being process. If the some other non-MF (windows/unix) system is FTP'ing then use the SITE command to create the correct LRECL and RECFM so that the data may not truncate.

Hope this helps

arvibala · Beginner Joined: 12 Feb 2008 Posts: 142 Topics: 67

Hi jsharon1248 / Ravi,

The Team who is sending us the File was not able to allocate the File, so they want us to Pre-Allocate, so that they can Just send data.

Kolusu,
I dont agree with your option, because the FTP step at the Oracle Team is failing. They will send us the data anytime in the last week of the month, so thought if we had some option to allocate dataset which doesnt migrate.

Am I expecting too much? Wink

_________________
Arvind
"You can make a difference with your smile. Have that with you always"

expat · Posted: Fri Jan 09, 2009 2:49 am Post subject:

As previously stated, talk to your storage team who can easily change the MGMTCLAS of the dataset to non migrate, or migrate after nn days nonuse.

Do it once and it is done for ever !
_________________
If it's true that we are here to help others,
then what exactly are the others here for ?