|
View previous topic :: View next topic
|
| Author |
Message |
l.nethaji
New User
Joined: 16 Mar 2008 Posts: 90 Location: tamil nadu
|
|
|
|
Hi,
I am trying the use the INDD parameters in the OUTDD parameter in IDCAMS utility.
Please let me know if ther is any option like DCB=*.SORTIN as like in sort which in IDCAMS where i prevent the LRECL changes in the future.
Regards,
L.Nethaji |
|
| Back to top |
|
 |
Bill Woodger
Moderator Emeritus
Joined: 09 Mar 2011 Posts: 7309 Location: Inside the Matrix
|
|
|
|
In the JCL, you want to refer back to an existing file to get an automatic copy of some information? Like you've already done in SORT?
Did you try it? Can't imagine it'll do any damage if you can't. Give it a go.
Look it up in the JCL manual. Try "Backward Reference" in the Index. |
|
| Back to top |
|
 |
superk
Global Moderator

Joined: 26 Apr 2004 Posts: 4652 Location: Raleigh, NC, USA
|
|
|
|
| Of course, the bigger question is, if you already use and are familiar with your SORT tool, why bother with IDCAMS? |
|
| Back to top |
|
 |
l.nethaji
New User
Joined: 16 Mar 2008 Posts: 90 Location: tamil nadu
|
|
|
|
Bill,
I tried running the below JCL .I tried to run the IDCAMS utility to copy the VSAM file into a flat file .I encountered the below error message
STMT NO. MESSAGE
4 IEF642I EXCESSIVE PARAMETER LENGTH IN THE DSNAME FIELD
TM1455I 2011.167 13:35:52 JOB EXT1RXKC FAILED, JCL ERROR
JCL:
//EXT1RXKC JOB (P091,0000),'P0913ACC PROC',
// CLASS=1,MSGCLASS=5,MSGLEVEL=(1,1),NOTIFY=EXT1RXK
//************************************************************
//SN091005 EXEC PGM=IDCAMS,REGION=4096K,COND=(0,NE)
//INDD DD DSN=TEST.N091V.TRN13CLN.SN091055.N091MTD,
// DISP=SHR
//OUTDD DD DSN=EXT.N091V.TRN13CLN.N091MTD22,
// DISP=(NEW,CATLG,DELETE),
// UNIT=DISK,
// SPACE=(CYL,(4900,1200),RLSE),
// DCB=(LRECL=224,BLKSIZE=0,RECFM=FB)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
REPRO INFILE(INDD) OUTFILE(OUTDD)
//
Please correct if am wrong.
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.
Regards,
L.Nethaji |
|
| Back to top |
|
 |
Robert Sample
Global Moderator

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. |
|
| Back to top |
|
 |
l.nethaji
New User
Joined: 16 Mar 2008 Posts: 90 Location: tamil nadu
|
|
|
|
Robert ,
I changes the dataset name as you suggested .
But i encountered the storage problem . It says like more than 100 cyl cant be allocated to TSO POOL.
So i chnged the Cyclinder size to 50,50 as prim and sec.
But when i tried to open the dataset it gives an invalid block size as a error message.
I even tried to comment out the DCB parameters so that i thought the system will take its own based on the input but still it gives maxcc=12.
Please help
JCL:
//SN091005 EXEC PGM=IDCAMS,REGION=4096K,COND=(0,NE)
//INDD DD DSN=TEST.N091V.TRN13CLN.SN091055.N091MTD,
// DISP=SHR
//OUTDD DD DSN=EXT.N091V.TRN13CLN.N091MT7,
// DISP=(NEW,CATLG,DELETE),
// UNIT=DISK,
// SPACE=(CYL,(50,50),RLSE),
// DCB=(LRECL=224,BLKSIZE=0,RECFM=FB)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
----+----1----+----2----+----3----+----4----+----5----+----6----+----7
REPRO INFILE(INDD) OUTFILE(OUTDD)
**WARNING - DSS5572W - DCB MISSING FROM REPRO OUTFILE DD STATEMENT
//
Regards,
L.Nethaji |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus

Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
|
|
|
|
Post the jcl and control statements for the sort process that works. Maybe there is some difference that is not obvious.
Oh, yeah, why chase down this idcams process when it already works (better) with sort
d |
|
| Back to top |
|
 |
Akatsukami
Global Moderator

Joined: 03 Oct 2009 Posts: 1787 Location: Bloomington, IL
|
|
|
|
| DSS5572W is an ASG JOB/SCAN message, not an actual IDCAMS message, isn't it? |
|
| Back to top |
|
 |
Robert Sample
Global Moderator

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:
| Code: |
//ALLOCFIL EXEC PGM=IEFBR14
//OUTDD DD DSN=EXT.N091V.TRN13CLN.N091MT7,
// DISP=(NEW,CATLG,DELETE),
// UNIT=DISK,
// SPACE=(CYL,(50,50),RLSE),
// DCB=(LRECL=224,BLKSIZE=0,RECFM=FB)
//SN091005 EXEC PGM=IDCAMS,REGION=4096K,COND=(0,NE)
//INDD DD DSN=TEST.N091V.TRN13CLN.SN091055.N091MTD,
// DISP=SHR
//OUTDD DD DSN=EXT.N091V.TRN13CLN.N091MT7,
// DISP=OLD
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
REPRO INFILE(INDD) OUTFILE(OUTDD)
/* |
but based on what you've posted so far, I don't hink there's a high chance of this working. |
|
| Back to top |
|
 |
enrico-sorichetti
Superior Member

Joined: 14 Mar 2007 Posts: 10902 Location: italy
|
|
|
|
| Quote: |
| DSS5572W - DCB MISSING FROM REPRO OUTFILE DD STATEMENT |
posting any jcl checker messages is just a waste of time for everybody.
come back only when You can post real JCL messages |
|
| Back to top |
|
 |
Dsingh29
Active User

Joined: 16 Dec 2008 Posts: 132 Location: IBM
|
|
|
|
Hi There,
below code works perfectly for me, try removing the blksize and come back with your results.
| Code: |
//SN091005 EXEC PGM=IDCAMS,REGION=4096K,COND=(0,NE)
//INDD DD DSN=XXX.JXXX.XXXX.T1706,
// DISP=SHR
//OUTDD DD DSN=XXXX.JXXXX.XXXX.T1606.TEST1,
// DISP=(NEW,CATLG,DELETE),
// UNIT=SYSDA,
// SPACE=(CYL,(50,50),RLSE),
// DCB=(LRECL=643,RECFM=VB)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
REPRO -
INFILE(INDD) -
OUTFILE(OUTDD)
/* |
|
|
| Back to top |
|
 |
prasanth_thavva
New User

Joined: 28 Jul 2005 Posts: 86 Location: Chennai
|
|
|
|
| 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 ? |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus

Joined: 23 Nov 2006 Posts: 19243 Location: Inside the Matrix
|
|
|
|
Hello,
| Code: |
| **WARNING - DSS5572W - DCB MISSING FROM REPRO OUTFILE DD STATEMENT |
| Quote: |
| Kindly let me know BLKSIZE=0 is the reason for JCL execution failure, |
You have not posted any "jcl executon failure". As others have mentioned, the DSS5572W is a warning from a jcl checker - not a jcl error.
Once again, why are you not putting your effort into the better solution using sort? |
|
| Back to top |
|
 |
Robert Sample
Global Moderator

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. |
|
| Back to top |
|
 |
prasanth_thavva
New User

Joined: 28 Jul 2005 Posts: 86 Location: Chennai
|
|
|
|
Based on this below message , I have raised my query ,
"below code works perfectly for me, try removing the blksize and come back with your results."
i can understand the BLKSIZE is not related to IDCAMS and also BLKSIZE =0 means ...etc
when i saw the above post i got doubt by removing blksize how he resolved the issue.
Thanks once again for ur detail understanding and explanation
Thanks
Prasanth |
|
| Back to top |
|
 |
Robert Sample
Global Moderator

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. |
|
| Back to top |
|
 |
jasorn Warnings : 1 Active User
Joined: 12 Jul 2006 Posts: 191 Location: USA
|
|
|
|
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. |
|
|
| Back to top |
|
 |
|
|
 |
All times are GMT + 6 Hours |
|