z/OS (kind of off topic)

Philip Sevetson

z/OS (kind of off topic)
**please note my email address change**
I haven't done nested JCL PROC calls yet. I recall reading that it became permitted several releases ago. Does anyone do it?

I've got a JCL stream calling a PROC which is nine steps, each of which does the same thing (COBOL, EXEC SQL INSERTs), with a slightly different input filename (something.FILE01, something.FILE02, ...). I could eliminate the repetitive coding by nesting my calls. Are there any tricks or 'gotcha's?

Philip Sevetson
Computer Systems Manager
450 West 33rd Street
New York, NY 10001
212-857-1688 w
917-991-7052 c
212-857-1659 f
[cid:[login to unmask email]

**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
Attachments

  • image001.png (3.3k)

Lizette Koehler

z/OS (kind of off topic)
(in response to Philip Sevetson)

Just be very careful.  You cannot over ride nested procs.  Even symbolics can be a challenge getting them into the nested proc.

My advice would be not to use them unless you are okay with updating procs to fix issues.

I have opened an RFE and SR to IBM on nested procs and there is just no way for them to be over-ridden. 


Lizette


-----Original Message-----
From: "Sevetson, Phil"
Sent: Mar 1, 2017 11:54 AM
To: "[login to unmask email]"
Subject: [DB2-L] - z/OS (kind of off topic)

**please note my email address change**I haven’t done nested JCL PROC calls yet. I recall reading that it became permitted several releases ago. Does anyone do it? I’ve got a JCL stream calling a PROC which is nine steps, each of which does the same thing (COBOL, EXEC SQL INSERTs), with a slightly different input filename (something.FILE01, something.FILE02, ...). I could eliminate the repetitive coding by nesting my calls.  Are there any tricks or ‘gotcha’s? Philip SevetsonComputer Systems Manager450 West 33rd StreetNew York, NY 10001212-857-1688 w917-991-7052 c212-857-1659 f **This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
Attachment Links: image001.png (3 k)  
Site Links: View post online   View mailing list online   Start new thread via email   Unsubscribe from this mailing list   Manage your subscription  

This email has been sent to: [login to unmask email]
** ** ** Attend the 2017 IDUG Data Tech Summit ** ** **
---> Anaheim, California, May 1 - May 2, 2017 <---
http://www.idug.org/page/dts2017


Use of this email content is governed by the terms of service at:
http://www.idug.org/p/cm/ld/fid=2

Lizette Koehler

z/OS (kind of off topic)
(in response to Philip Sevetson)

So are you considering

Case 1:
  Proc A
     Proc B  Contained in PROC A
        Proc C   Contained in PROC B

Or Case 2
  Proc A with 9 steps

//S1 EXEC PROCA,DSN=,Var1=var2=
//S2 exec proca,dsn=.var1=,var2=

And so forth

What do you consider nested?  Case 1 where PROCA calls PROCB calls PROCC
or case2 where there is a common proc and just vars need to be changed for each execution?

Lizette

-----Original Message-----
From: Lizette Koehler
Sent: Mar 1, 2017 2:51 PM
To: [login to unmask email], "[login to unmask email]"
Subject: [DB2-L] - RE: z/OS (kind of off topic)


Just be very careful.  You cannot over ride nested procs.  Even symbolics can be a challenge getting them into the nested proc.

My advice would be not to use them unless you are okay with updating procs to fix issues.

I have opened an RFE and SR to IBM on nested procs and there is just no way for them to be over-ridden. 


Lizette


-----Original Message-----
From: "Sevetson, Phil"
Sent: Mar 1, 2017 11:54 AM
To: "[login to unmask email]"
Subject: [DB2-L] - z/OS (kind of off topic)

**please note my email address change**I haven’t done nested JCL PROC calls yet. I recall reading that it became permitted several releases ago. Does anyone do it? I’ve got a JCL stream calling a PROC which is nine steps, each of which does the same thing (COBOL, EXEC SQL INSERTs), with a slightly different input filename (something.FILE01, something.FILE02, ...). I could eliminate the repetitive coding by nesting my calls.  Are there any tricks or ‘gotcha’s? Philip SevetsonComputer Systems Manager450 West 33rd StreetNew York, NY 10001212-857-1688 w917-991-7052 c212-857-1659 f **This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----
Site Links: View post online   View mailing list online   Start new thread via email   Unsubscribe from this mailing list   Manage your subscription  

This email has been sent to: [login to unmask email]
** ** ** Attend the 2017 IDUG Data Tech Summit ** ** **
---> Anaheim, California, May 1 - May 2, 2017 <---
http://www.idug.org/page/dts2017


Use of this email content is governed by the terms of service at:
http://www.idug.org/p/cm/ld/fid=2

Tony Saul

z/OS (kind of off topic)
(in response to Philip Sevetson)
Our CICS region procs invoke a standard CICS proc passing variables to make them unique, I also use that on the MQ Queue Manager
//XXXCICZ0 PROC OUTC='*',  //             ENV=XXX0,   //             RGN=512M,   //             SYSNM=XXXZ, //             START=AUTO  //CICSV520 EXEC   CICSV520,SYSNM=&SYSNM,ENV=&ENV,START=&START,RGN=&RGN

//CICSV520 PROC OUTC='*', //             OUTD='*',  //             ENV=,      //             SYSNM=,    //             RGN=1150M, //             START=AUTO 
And the CICSV520 proc has 8 or 10 steps.
Is that what you meant? 
Regards, Tony

On Thursday, 2 March 2017, 5:24, "Sevetson, Phil" <[login to unmask email]> wrote:


<!--#yiv3399765700 _filtered #yiv3399765700 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv3399765700 {font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}#yiv3399765700 #yiv3399765700 p.yiv3399765700MsoNormal, #yiv3399765700 li.yiv3399765700MsoNormal, #yiv3399765700 div.yiv3399765700MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", "sans-serif";}#yiv3399765700 a:link, #yiv3399765700 span.yiv3399765700MsoHyperlink {color:blue;text-decoration:underline;}#yiv3399765700 a:visited, #yiv3399765700 span.yiv3399765700MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv3399765700 p.yiv3399765700MsoAcetate, #yiv3399765700 li.yiv3399765700MsoAcetate, #yiv3399765700 div.yiv3399765700MsoAcetate {margin:0in;margin-bottom:.0001pt;font-size:8.0pt;font-family:"Tahoma", "sans-serif";}#yiv3399765700 span.yiv3399765700EmailStyle17 {font-family:"Calibri", "sans-serif";color:windowtext;}#yiv3399765700 span.yiv3399765700BalloonTextChar {font-family:"Tahoma", "sans-serif";}#yiv3399765700 .yiv3399765700MsoChpDefault {font-family:"Calibri", "sans-serif";} _filtered #yiv3399765700 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv3399765700 div.yiv3399765700WordSection1 {}-->**please note my email address change**I haven’t done nested JCL PROC calls yet. I recall reading that it became permitted several releases ago. Does anyone do it?   I’ve got a JCL stream calling a PROC which is nine steps, each of which does the same thing (COBOL, EXEC SQL INSERTs), with a slightly different input filename (something.FILE01, something.FILE02, ...). I could eliminate the repetitive coding by nesting my calls.  Are there any tricks or ‘gotcha’s?   Philip Sevetson Computer Systems Manager 450 West 33rd Street New York, NY 10001 212-857-1688 w 917-991-7052 c 212-857-1659 f   **This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
Attachment Links: image001.png (3 k)  
Site Links: View post online   View mailing list online   Start new thread via email   Unsubscribe from this mailing list   Manage your subscription  

This email has been sent to: [login to unmask email]** ** ** Attend the 2017 IDUG Data Tech Summit ** ** **
---> Anaheim, California, May 1 - May 2, 2017 <---
http://www.idug.org/page/dts2017

Use of this email content is governed by the terms of service at:
http://www.idug.org/p/cm/ld/fid=2

Chris Blaicher

z/OS (kind of off topic)
(in response to Lizette Koehler)
There is still the limit on the number of steps in a job, or at least there was.
As I recall it was 256 steps per job.

Chris Blaicher
Technical Architect
Mainframe Development
Syncsort Incorporated
2 Blue Hill Plaza #1563, Pearl River, NY 10965

P: 201-930-8234 | M: 512-627-3803
E: [login to unmask email]

www.syncsort.comhttp://www.syncsort.com

CONNECTING BIG IRON TO BIG DATA

From: Lizette Koehler [mailto:[login to unmask email]
Sent: Wednesday, March 1, 2017 4:59 PM
To: [login to unmask email]
Subject: [DB2-L] - RE: z/OS (kind of off topic)


So are you considering

Case 1:
Proc A
Proc B Contained in PROC A
Proc C Contained in PROC B

Or Case 2
Proc A with 9 steps

//S1 EXEC PROCA,DSN=,Var1=var2=
//S2 exec proca,dsn=.var1=,var2=

And so forth

What do you consider nested? Case 1 where PROCA calls PROCB calls PROCC
or case2 where there is a common proc and just vars need to be changed for each execution?

Lizette
-----Original Message-----
From: Lizette Koehler
Sent: Mar 1, 2017 2:51 PM
To: [login to unmask email]<mailto:[login to unmask email]>, "[login to unmask email]<mailto:[login to unmask email]>"
Subject: [DB2-L] - RE: z/OS (kind of off topic)



Just be very careful. You cannot over ride nested procs. Even symbolics can be a challenge getting them into the nested proc.

My advice would be not to use them unless you are okay with updating procs to fix issues.

I have opened an RFE and SR to IBM on nested procs and there is just no way for them to be over-ridden.


Lizette

-----Original Message-----
From: "Sevetson, Phil"
Sent: Mar 1, 2017 11:54 AM
To: "[login to unmask email]<mailto:[login to unmask email]>"
Subject: [DB2-L] - z/OS (kind of off topic)

**please note my email address change**
I haven’t done nested JCL PROC calls yet. I recall reading that it became permitted several releases ago. Does anyone do it?

I’ve got a JCL stream calling a PROC which is nine steps, each of which does the same thing (COBOL, EXEC SQL INSERTs), with a slightly different input filename (something.FILE01, something.FILE02, ...). I could eliminate the repetitive coding by nesting my calls. Are there any tricks or ‘gotcha’s?

Philip Sevetson
Computer Systems Manager
450 West 33rd Street
New York, NY 10001
212-857-1688 w
917-991-7052 c
212-857-1659 f
[cid:[login to unmask email]

**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----

-----End Original Message-----

-----End Original Message-----

________________________________



ATTENTION: -----

The information contained in this message (including any files transmitted with this message) may contain proprietary, trade secret or other confidential and/or legally privileged information. Any pricing information contained in this message or in any files transmitted with this message is always confidential and cannot be shared with any third parties without prior written approval from Syncsort. This message is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any use, disclosure, copying or distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and/or Syncsort and destroy all copies of this message in your possession, custody or control.

Philip Sevetson

z/OS (kind of off topic)
(in response to Tony Saul)
**please note my email address change**
Tony:
This is what I had in mind, yes. Thank you ☺

Philip Sevetson
Computer Systems Manager
450 West 33rd Street
New York, NY 10001
212-857-1688 w
917-991-7052 c
212-857-1659 f
[cid:[login to unmask email]

From: Tony Saul [mailto:[login to unmask email]
Sent: Wednesday, March 01, 2017 5:48 PM
To: [login to unmask email]
Subject: [DB2-L] - RE: z/OS (kind of off topic)

Our CICS region procs invoke a standard CICS proc passing variables to make them unique, I also use that on the MQ Queue Manager

//XXXCICZ0 PROC OUTC='*',
// ENV=XXX0,
// RGN=512M,
// SYSNM=XXXZ,
// START=AUTO
//CICSV520 EXEC CICSV520,SYSNM=&SYSNM,ENV=&ENV,START=&START,RGN=&RGN

//CICSV520 PROC OUTC='*',
// OUTD='*',
// ENV=,
// SYSNM=,
// RGN=1150M,
// START=AUTO

And the CICSV520 proc has 8 or 10 steps.

Is that what you meant?

Regards, Tony

On Thursday, 2 March 2017, 5:24, "Sevetson, Phil" <[login to unmask email]<mailto:[login to unmask email]>> wrote:

**please note my email address change**
I haven’t done nested JCL PROC calls yet. I recall reading that it became permitted several releases ago. Does anyone do it?

I’ve got a JCL stream calling a PROC which is nine steps, each of which does the same thing (COBOL, EXEC SQL INSERTs), with a slightly different input filename (something.FILE01, something.FILE02, ...). I could eliminate the repetitive coding by nesting my calls. Are there any tricks or ‘gotcha’s?

Philip Sevetson
Computer Systems Manager
450 West 33rd Street
New York, NY 10001
212-857-1688 w
917-991-7052 c
212-857-1659 f

**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
Attachments

  • image001.png (3.3k)

Philip Sevetson

z/OS (kind of off topic)
(in response to Lizette Koehler)
**please note my email address change**
Lizette,
Case 2 is what I am (was) considering. We found a simpler way to solve the problem (and cut out about 95% of the text of the proc, including excess comments). However, I fully expect to be using stuff like this within the next year or two as well.

Philip Sevetson
Computer Systems Manager
450 West 33rd Street
New York, NY 10001
212-857-1688 w
917-991-7052 c
212-857-1659 f
[cid:[login to unmask email]

From: Lizette Koehler [mailto:[login to unmask email]
Sent: Wednesday, March 01, 2017 4:59 PM
To: [login to unmask email]
Subject: [DB2-L] - RE: z/OS (kind of off topic)


So are you considering

Case 1:
Proc A
Proc B Contained in PROC A
Proc C Contained in PROC B

Or Case 2
Proc A with 9 steps

//S1 EXEC PROCA,DSN=,Var1=var2=
//S2 exec proca,dsn=.var1=,var2=

And so forth

What do you consider nested? Case 1 where PROCA calls PROCB calls PROCC
or case2 where there is a common proc and just vars need to be changed for each execution?

Lizette
-----Original Message-----
From: Lizette Koehler
Sent: Mar 1, 2017 2:51 PM
To: [login to unmask email]<mailto:[login to unmask email]>, "[login to unmask email]<mailto:[login to unmask email]>"
Subject: [DB2-L] - RE: z/OS (kind of off topic)



Just be very careful. You cannot over ride nested procs. Even symbolics can be a challenge getting them into the nested proc.

My advice would be not to use them unless you are okay with updating procs to fix issues.

I have opened an RFE and SR to IBM on nested procs and there is just no way for them to be over-ridden.


Lizette

-----Original Message-----
From: "Sevetson, Phil"
Sent: Mar 1, 2017 11:54 AM
To: "[login to unmask email]<mailto:[login to unmask email]>"
Subject: [DB2-L] - z/OS (kind of off topic)

**please note my email address change**
I haven’t done nested JCL PROC calls yet. I recall reading that it became permitted several releases ago. Does anyone do it?

I’ve got a JCL stream calling a PROC which is nine steps, each of which does the same thing (COBOL, EXEC SQL INSERTs), with a slightly different input filename (something.FILE01, something.FILE02, ...). I could eliminate the repetitive coding by nesting my calls. Are there any tricks or ‘gotcha’s?

Philip Sevetson
Computer Systems Manager
450 West 33rd Street
New York, NY 10001
212-857-1688 w
917-991-7052 c
212-857-1659 f
[cid:[login to unmask email]

**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
-----End Original Message-----

-----End Original Message-----

-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
Attachments

  • image001.png (3.3k)