Re: IEBCOPY & PARM='WORK=xxMB'
On Wed, Sep 1, 2021 at 11:39 AM PINION, RICHARD W. wrote: > > // JOB (Y),RPINION,CLASS=2,MSGCLASS=O, > JOB17827 > // NOTIFY=,COND=(0,LT),REGION=128M > IEFC653I SUBSTITUTION JCL - > (Y),RPINION,CLASS=2,MSGCLASS=O,NOTIFY=ZZ,COND=(0,LT),REGION=128M > //BACK1 EXEC PGM=IEBCOPY,PARM='WORK=8M,CMWA=8190K' > > CPU: 0 HR 00 MIN 00.68 SECSRB: 0 HR 00 MIN 00.03 SEC > VIRT: 8352K SYS: 300K EXT:4K SYS:17476K > ATB- REAL: 1056K SLOTS: 0K > VIRT- ALLOC: 13M SHRD: 0M > VIRT: 8352K EXT:4K Looks like the parm is limiting use to 8M. Instead of REGION=nM, you might try REGIONX=(24K,31M,64G) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBCOPY & PARM='WORK=xxMB'
Classification: Confidential 1) I run all if my batch jobs with a region of 256M. I suggest that (at least in this particular case ) the you do the same. 2) last I heard IEBCOPY does a conditional getmain for 1.5M, so work=8M is an increase 3) In conjunction with the region increase, increase work= to 32M (or even higher if required) HTH, IEB1011E AVAILABLE STORAGE (4K) IS TOO SMALL. ADD 7779K MORE BYTES TO WORK SIZE. And this is the EXEC statement for the IEBCOPY. EXEC PGM=IEBCOPY,PARM='WORK=8M' Our below the line private area is about 8.5 Meg. I have REGION=32M on the job statement. ::DISCLAIMER:: The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBCOPY & PARM='WORK=xxMB'
// JOB (Y),RPINION,CLASS=2,MSGCLASS=O, JOB17827 // NOTIFY=,COND=(0,LT),REGION=128M IEFC653I SUBSTITUTION JCL - (Y),RPINION,CLASS=2,MSGCLASS=O,NOTIFY=ZZ,COND=(0,LT),REGION=128M //BACK1 EXEC PGM=IEBCOPY,PARM='WORK=8M,CMWA=8190K' CPU: 0 HR 00 MIN 00.68 SECSRB: 0 HR 00 MIN 00.03 SEC VIRT: 8352K SYS: 300K EXT:4K SYS:17476K ATB- REAL: 1056K SLOTS: 0K VIRT- ALLOC: 13M SHRD: 0M -Original Message- From: IBM Mainframe Discussion List On Behalf Of Mike Schwab Sent: Wednesday, September 1, 2021 12:34 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEBCOPY & PARM='WORK=xxMB' [External Email. Exercise caution when clicking links or opening attachments.] On the step completion message, what are your memory usage? On Wed, Sep 1, 2021 at 10:09 AM Steve Smith wrote: > > There's no reason to concatenate the unload files, just do two COPY > operations (which can be in the same step, in case that's not obvious). > > REGION=32M, really? This isn't 1990. How about 1000M? > > sas > > > On Wed, Sep 1, 2021 at 10:54 AM PINION, RICHARD W. > > wrote: > > > We are running z/OS 2.2 on z15. I am having a problem selectively > > unloading a very large PDS/E, over 2,000,000 tracks, and with > > several thousand members. The SYSIN to IEBCOPY has 174,000 SELECT > > statements. We are getting > > > > IEB1011E AVAILABLE STORAGE (4K) IS TOO SMALL. ADD 7779K MORE BYTES > > TO WORK SIZE. > > > > And this is the EXEC statement for the IEBCOPY. > > > > EXEC PGM=IEBCOPY,PARM='WORK=8M' > > > > Our below the line private area is about 8.5 Meg. I have REGION=32M > > on the job statement. > > > > I have tried various combinations of REGION=xxxM on the job > > statement, and increases in the WORK parm value. I cannot get around the > > error. > > > > One thing I am trying now is to use two steps, assigning ½ of the > > SELECT statements to the first step, and the remainder to the second > > step. I am creating two separate unload datasets using this method. > > I suspect that one cannot concatenate IEBCOPY UNLOAD datasets when > > reloading the PDS/E. > > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBCOPY & PARM='WORK=xxMB'
On the step completion message, what are your memory usage? On Wed, Sep 1, 2021 at 10:09 AM Steve Smith wrote: > > There's no reason to concatenate the unload files, just do two COPY > operations (which can be in the same step, in case that's not obvious). > > REGION=32M, really? This isn't 1990. How about 1000M? > > sas > > > On Wed, Sep 1, 2021 at 10:54 AM PINION, RICHARD W. > wrote: > > > We are running z/OS 2.2 on z15. I am having a problem selectively > > unloading a very large > > PDS/E, over 2,000,000 tracks, and with several thousand members. The > > SYSIN to IEBCOPY > > has 174,000 SELECT statements. We are getting > > > > IEB1011E AVAILABLE STORAGE (4K) IS TOO SMALL. ADD 7779K MORE BYTES TO > > WORK SIZE. > > > > And this is the EXEC statement for the IEBCOPY. > > > > EXEC PGM=IEBCOPY,PARM='WORK=8M' > > > > Our below the line private area is about 8.5 Meg. I have REGION=32M on > > the job > > statement. > > > > I have tried various combinations of REGION=xxxM on the job statement, and > > increases in the WORK parm value. I cannot get around the error. > > > > One thing I am trying now is to use two steps, assigning ½ of the SELECT > > statements > > to the first step, and the remainder to the second step. I am creating > > two separate > > unload datasets using this method. I suspect that one cannot concatenate > > IEBCOPY > > UNLOAD datasets when reloading the PDS/E. > > > > > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBCOPY & PARM='WORK=xxMB'
I've never selectively included that many member, but maybe you can exclude members that you do not want to copy? are you using a copymod statement ? maybe specify CMWA=8190K and a region size greater that 32M? size is another parm option SIZE=nK or nM Carmen On 9/1/2021 10:30 AM, PINION, RICHARD W. wrote: Indeed I did. And, it had no effect. As for SAS's comment for using REGION=1000M, while I didn't go that high, increasing REGION on the job statement had no effect either. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lennie Dymoke-Bradshaw Sent: Wednesday, September 1, 2021 11:13 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEBCOPY & PARM='WORK=xxMB' [External Email. Exercise caution when clicking links or opening attachments.] Have you looked at using the spill data sets on SYSUT3 and SYSUT4? Lennie Dymoke-Bradshaw https://urldefense.com/v3/__https://rsclweb.com__;!!HnnddUIWDII9UQ!BoyjGzxrM4lde-pxf-y3TmqAQ1Q6v2YBIANM33UknReh8LQGYtyA5jcHAH2sM0X-whU$ 'Dance like no one is watching. Encrypt like everyone is.' -Original Message- From: IBM Mainframe Discussion List On Behalf Of PINION, RICHARD W. Sent: 01 September 2021 15:54 To: IBM-MAIN@LISTSERV.UA.EDU Subject: IEBCOPY & PARM='WORK=xxMB' We are running z/OS 2.2 on z15. I am having a problem selectively unloading a very large PDS/E, over 2,000,000 tracks, and with several thousand members. The SYSIN to IEBCOPY has 174,000 SELECT statements. We are getting IEB1011E AVAILABLE STORAGE (4K) IS TOO SMALL. ADD 7779K MORE BYTES TO WORK SIZE. And this is the EXEC statement for the IEBCOPY. EXEC PGM=IEBCOPY,PARM='WORK=8M' Our below the line private area is about 8.5 Meg. I have REGION=32M on the job statement. I have tried various combinations of REGION=xxxM on the job statement, and increases in the WORK parm value. I cannot get around the error. One thing I am trying now is to use two steps, assigning ½ of the SELECT statements to the first step, and the remainder to the second step. I am creating two separate unload datasets using this method. I suspect that one cannot concatenate IEBCOPY UNLOAD datasets when reloading the PDS/E. Any help or suggestions would be greatly appreciated. Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- /I am not bound to win, but I am bound to be true. I am not bound to succeed, but I am bound to live by the light that I have. I must stand with anybody that stands right, and stand with him while he is right, and part with him when he goes wrong. *Abraham Lincoln*/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBCOPY & PARM='WORK=xxMB'
Indeed I did. And, it had no effect. As for SAS's comment for using REGION=1000M, while I didn't go that high, increasing REGION on the job statement had no effect either. -Original Message- From: IBM Mainframe Discussion List On Behalf Of Lennie Dymoke-Bradshaw Sent: Wednesday, September 1, 2021 11:13 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: IEBCOPY & PARM='WORK=xxMB' [External Email. Exercise caution when clicking links or opening attachments.] Have you looked at using the spill data sets on SYSUT3 and SYSUT4? Lennie Dymoke-Bradshaw https://urldefense.com/v3/__https://rsclweb.com__;!!HnnddUIWDII9UQ!BoyjGzxrM4lde-pxf-y3TmqAQ1Q6v2YBIANM33UknReh8LQGYtyA5jcHAH2sM0X-whU$ 'Dance like no one is watching. Encrypt like everyone is.' -Original Message- From: IBM Mainframe Discussion List On Behalf Of PINION, RICHARD W. Sent: 01 September 2021 15:54 To: IBM-MAIN@LISTSERV.UA.EDU Subject: IEBCOPY & PARM='WORK=xxMB' We are running z/OS 2.2 on z15. I am having a problem selectively unloading a very large PDS/E, over 2,000,000 tracks, and with several thousand members. The SYSIN to IEBCOPY has 174,000 SELECT statements. We are getting IEB1011E AVAILABLE STORAGE (4K) IS TOO SMALL. ADD 7779K MORE BYTES TO WORK SIZE. And this is the EXEC statement for the IEBCOPY. EXEC PGM=IEBCOPY,PARM='WORK=8M' Our below the line private area is about 8.5 Meg. I have REGION=32M on the job statement. I have tried various combinations of REGION=xxxM on the job statement, and increases in the WORK parm value. I cannot get around the error. One thing I am trying now is to use two steps, assigning ½ of the SELECT statements to the first step, and the remainder to the second step. I am creating two separate unload datasets using this method. I suspect that one cannot concatenate IEBCOPY UNLOAD datasets when reloading the PDS/E. Any help or suggestions would be greatly appreciated. Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBCOPY & PARM='WORK=xxMB'
Have you looked at using the spill data sets on SYSUT3 and SYSUT4? Lennie Dymoke-Bradshaw https://rsclweb.com Dance like no one is watching. Encrypt like everyone is. -Original Message- From: IBM Mainframe Discussion List On Behalf Of PINION, RICHARD W. Sent: 01 September 2021 15:54 To: IBM-MAIN@LISTSERV.UA.EDU Subject: IEBCOPY & PARM='WORK=xxMB' We are running z/OS 2.2 on z15. I am having a problem selectively unloading a very large PDS/E, over 2,000,000 tracks, and with several thousand members. The SYSIN to IEBCOPY has 174,000 SELECT statements. We are getting IEB1011E AVAILABLE STORAGE (4K) IS TOO SMALL. ADD 7779K MORE BYTES TO WORK SIZE. And this is the EXEC statement for the IEBCOPY. EXEC PGM=IEBCOPY,PARM='WORK=8M' Our below the line private area is about 8.5 Meg. I have REGION=32M on the job statement. I have tried various combinations of REGION=xxxM on the job statement, and increases in the WORK parm value. I cannot get around the error. One thing I am trying now is to use two steps, assigning ½ of the SELECT statements to the first step, and the remainder to the second step. I am creating two separate unload datasets using this method. I suspect that one cannot concatenate IEBCOPY UNLOAD datasets when reloading the PDS/E. Any help or suggestions would be greatly appreciated. Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IEBCOPY & PARM='WORK=xxMB'
There's no reason to concatenate the unload files, just do two COPY operations (which can be in the same step, in case that's not obvious). REGION=32M, really? This isn't 1990. How about 1000M? sas On Wed, Sep 1, 2021 at 10:54 AM PINION, RICHARD W. wrote: > We are running z/OS 2.2 on z15. I am having a problem selectively > unloading a very large > PDS/E, over 2,000,000 tracks, and with several thousand members. The > SYSIN to IEBCOPY > has 174,000 SELECT statements. We are getting > > IEB1011E AVAILABLE STORAGE (4K) IS TOO SMALL. ADD 7779K MORE BYTES TO > WORK SIZE. > > And this is the EXEC statement for the IEBCOPY. > > EXEC PGM=IEBCOPY,PARM='WORK=8M' > > Our below the line private area is about 8.5 Meg. I have REGION=32M on > the job > statement. > > I have tried various combinations of REGION=xxxM on the job statement, and > increases in the WORK parm value. I cannot get around the error. > > One thing I am trying now is to use two steps, assigning ½ of the SELECT > statements > to the first step, and the remainder to the second step. I am creating > two separate > unload datasets using this method. I suspect that one cannot concatenate > IEBCOPY > UNLOAD datasets when reloading the PDS/E. > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IEBCOPY & PARM='WORK=xxMB'
We are running z/OS 2.2 on z15. I am having a problem selectively unloading a very large PDS/E, over 2,000,000 tracks, and with several thousand members. The SYSIN to IEBCOPY has 174,000 SELECT statements. We are getting IEB1011E AVAILABLE STORAGE (4K) IS TOO SMALL. ADD 7779K MORE BYTES TO WORK SIZE. And this is the EXEC statement for the IEBCOPY. EXEC PGM=IEBCOPY,PARM='WORK=8M' Our below the line private area is about 8.5 Meg. I have REGION=32M on the job statement. I have tried various combinations of REGION=xxxM on the job statement, and increases in the WORK parm value. I cannot get around the error. One thing I am trying now is to use two steps, assigning ½ of the SELECT statements to the first step, and the remainder to the second step. I am creating two separate unload datasets using this method. I suspect that one cannot concatenate IEBCOPY UNLOAD datasets when reloading the PDS/E. Any help or suggestions would be greatly appreciated. Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution, or copying of this e-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this e-mail message from your computer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
