Parallely As u suggested i tried to find the backward reference in the JCL guide in google search for IDCAMS . i didnt encounter get any example in search engine as like for my previous query.
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
1. Every data set name is limited to at most 8 characters between periods. Your last node on OUTDD has 9 characters.
2. Depending upon your release of z/OS and your site's storage management policies, be aware that your job may fail with a storage abend after you correct the data set name syntax error. Up through (IIRC) z/OS 1.10, sequential data sets were limited to 65535 tracks and 4900 cylinders as your primary for OUTDD is 73500 tracks.
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
You would do best by spending time with your site support group, team leader, or coworkers to find out the site standards. I don't recognize DSS5572W as an IBM message, which means your site is NOT using the usual IBM standard software. Since the site could be using anything, it is not possible to precisely identify the source of your problem.
And, please, learn to use the Code tag to post JCL -- it preserves spaces which your post didn't.
You might try preallocating the output data set like this:
Kindly let me know BLKSIZE=0 is the reason for JCL execution failure, BLKSIZE = 0 gives the sytem to decide the BLKSIZE at run time. or BLKSIZE not required parameter in IDCAMS utility ?
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
Quote:
Kindly let me know BLKSIZE=0 is the reason for JCL execution failure, BLKSIZE = 0 gives the system to decide the BLKSIZE at run time. or BLKSIZE not required parameter in IDCAMS utility ?
First, BLKSIZE=0 tells the system to determine the block size -- it is not going to cause any kind of problem.
Second, BLKSIZE is never used "in IDCAMS utility" -- IDCAMS requires control cards (such as DUMP, EXPORT, REPRO, PRINT, DEFINE). The BLKSIZE parameter is used in JCL, which can execute IDCAMS. Hence BLKSIZE is not even part of IDCAMS.
Third, you have not yet posted ANYTHING that indicates your JCL has any execution problem. All you have done is show that a JCL checker does not like something about your JCL, and that means nothing. The only thing that counts is when you submit the job and get the system messages.
Fourth, based upon your complete lack of understanding of (1) IDCAMS, (2) JCL, (3) batch processing, and (4) z/OS operation -- along with your refusal to understand what you are told -- I highly recommend you stop posting on this forum and start using the Beginners and Students Forum instead as it is more likely to get you answers that you can use. This forum is for professionals and you have, very completely, demonstrated that you are not a professional.
Joined: 06 Jun 2008 Posts: 8700 Location: Dubuque, Iowa, USA
Perhaps Dsingh29 will explain what was meant -- especially since removing the block size would have nothing to do with getting a good REPRO, so the comments made in that post are pretty much useless and irrelevant to the issue. That you are focused on them, instead of paying attention to the advice and questions of the senior members and moderators of this board, is another indication that you need to go to the Beginners and Students forum.
Excuse me for replying to an old post. I don't mean to discount the "try the student' section part of Robert's reply". But BLKSIZE is used in IDCAMS. I didn't want people reading this thread to think BLKSIZE was never used in IDCAMS.
[quote="Robert Sample"]
Quote:
Second, BLKSIZE is never used "in IDCAMS utility" -- IDCAMS requires control cards (such as DUMP, EXPORT, REPRO, PRINT, DEFINE). The BLKSIZE parameter is used in JCL, which can execute IDCAMS. Hence BLKSIZE is not even part of IDCAMS.
