Re: Adventures in JCL: PROCs, symbols and instream data

2017-05-08 Thread Tom Marchant
On Fri, 5 May 2017 09:04:31 +1000, Andrew Rowley wrote: >On 4/05/2017 10:11 PM, Tom Marchant wrote: >> >> Did they say why it isn't supposed to work? >> Is there an undocumented restriction? >I am sure it *is* supposed to work, but it's easier to close a problem >as a user error. I agree that it

Re: Adventures in JCL: PROCs, symbols and instream data

2017-05-04 Thread Andrew Rowley
On 4/05/2017 10:11 PM, Tom Marchant wrote: Did they say why it isn't supposed to work? Is there an undocumented restriction? I am sure it *is* supposed to work, but it's easier to close a problem as a user error. I am also fairly sure that no-one who would actually know whether it was

Re: Adventures in JCL: PROCs, symbols and instream data

2017-05-04 Thread Tom Marchant
On Thu, 4 May 2017 10:40:46 +1000, Andrew Rowley wrote: >On 27/04/2017 10:54 PM, Tom Marchant wrote: >> Glad you got it to work, but it should have worked the way you had it. >> I hope you will open a Service Request to get it fixed. >I had forgotten how frustrating it is to open Service

Re: Adventures in JCL: PROCs, symbols and instream data

2017-05-03 Thread Andrew Rowley
On 27/04/2017 10:54 PM, Tom Marchant wrote: Glad you got it to work, but it should have worked the way you had it. I hope you will open a Service Request to get it fixed. I had forgotten how frustrating it is to open Service Requests. IBM has many brilliant people dedicated to improving z/OS.

Re: Adventures in JCL: PROCs, symbols and instream data

2017-05-02 Thread Andrew Rowley
On 2/05/2017 9:03 PM, Jantje. wrote: //JOB1 JOB CLASS=A, // MSGCLASS=H, // NOTIFY= // SET Q= //* //TEST PROC MESSAGE='Hello World' // SET MESSAGE= Nice... I'm not sure that it is any clearer, but very creative! -- Andrew Rowley Black Hill Software

Re: Adventures in JCL: PROCs, symbols and instream data

2017-05-02 Thread Elardus Engelbrecht
Jantje wrote: >Andrew Rowley wrote: >>Does anyone know of a neater way to do this (using JCL only)? Is there any >>way to avoid the need for the triple apostrophes? >// SET Q= >// SET MESSAGE= Hmmm, very interesting dirty, but beautiful little trick! Thanks Jantje! Much

Re: Adventures in JCL: PROCs, symbols and instream data

2017-05-02 Thread Jantje.
On Wed, 26 Apr 2017 15:14:27 +1000, Andrew Rowley wrote: > >Does anyone know of a neater way to do this (using JCL only)? Is there >any way to avoid the need for the triple apostrophes? > //JOB1 JOB CLASS=A, // MSGCLASS=H, // NOTIFY= //

Re: Adventures in JCL: PROCs, symbols and instream data

2017-04-27 Thread Andrew Rowley
On 27/04/2017 10:54 PM, Tom Marchant wrote: Glad you got it to work, but it should have worked the way you had it. I hope you will open a Service Request to get it fixed. I will, I am on the z/OS RDP so I had to confirm whether it was possible and the process. I now know how to do it. The

Re: Adventures in JCL: PROCs, symbols and instream data

2017-04-27 Thread Tom Marchant
On Thu, 27 Apr 2017 16:36:12 +1000, Andrew Rowley wrote: >On 27/04/2017 12:46 AM, Tom Marchant wrote: >> or SET MESSAGE= and change the references to to > >SET MESSAGE= seems to be the fix... > >This works for all combinations I have thrown at it: Glad you got it to work, but it should have

Re: Adventures in JCL: PROCs, symbols and instream data

2017-04-27 Thread Andrew Rowley
On 27/04/2017 12:46 AM, Tom Marchant wrote: or SET MESSAGE= and change the references to to SET MESSAGE= seems to be the fix... This works for all combinations I have thrown at it: //TEST PROC MESSAGE='''Hello World''' //SYMBOLS EXPORT SYMLIST=(MESSAGE) // SET MESSAGE= //S1

Re: Adventures in JCL: PROCs, symbols and instream data

2017-04-27 Thread Andrew Rowley
On 27/04/2017 12:46 AM, Tom Marchant wrote: This sounds similar to a problem that I had a while back. Do you have OA47958 applied? It is applied, however it is very interesting, including the very similar JCL for testing. Unfortunately, if I take their JCL and add some variation: //PROC1

Re: Adventures in JCL: PROCs, symbols and instream data

2017-04-26 Thread Paul Gilmartin
On Wed, 26 Apr 2017 05:07:39 -0700, Charles Mills wrote: >Move the EXPORT outside of the PROC and into the open JOB? > Is a SET within a PROC elaborated when the PROC is defined or when it is executed? What is the scope of a symbol SET within a PROC? Is an EXPORT within a PROC elaborated when

Re: Adventures in JCL: PROCs, symbols and instream data

2017-04-26 Thread Tom Marchant
On Wed, 26 Apr 2017 07:40:47 -0700, Lizette Koehler wrote: >So to help me understand your term Nested Proc > >I think of a nested proc as a proc calling a proc. Yes, that is what he has. PROC TEST includes EXEC INNER >Next, I agree with @Charles. Move the EXPORT and SET statements >outside of

Re: Adventures in JCL: PROCs, symbols and instream data

2017-04-26 Thread Tom Marchant
On Wed, 26 Apr 2017 15:14:27 +1000, Andrew Rowley wrote: >I am trying to create some JCL procedures using symbols in instream >data, with the ability to override the symbol using standard procedure >calling conventions. This sounds similar to a problem that I had a while back. Do you have

Re: Adventures in JCL: PROCs, symbols and instream data

2017-04-26 Thread Lizette Koehler
. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Andrew Rowley > Sent: Tuesday, April 25, 2017 10:14 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Adventures in JCL: PROCs, symbols and instream dat

Re: Adventures in JCL: PROCs, symbols and instream data

2017-04-26 Thread Charles Mills
Move the EXPORT outside of the PROC and into the open JOB? Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Andrew Rowley Sent: Tuesday, April 25, 2017 10:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Adventures in JCL: PROCs

Adventures in JCL: PROCs, symbols and instream data

2017-04-25 Thread Andrew Rowley
I am trying to create some JCL procedures using symbols in instream data, with the ability to override the symbol using standard procedure calling conventions. This almost works: //JOB1 JOB CLASS=A, // MSGCLASS=H, // NOTIFY= //* //TEST PROC MESSAGE='''Hello