Re: Hex (was: Stupid JCL question)

[Paul Gilmartin]

On Sun, 24 Dec 2023 14:18:34 -0600, Michael Oujesky wrote:

>Just as an aside, the default EBCDIC to ASCIIi translation table in
>FTP has issues with some special characters.  We used CONVXLAT
>against TCPIP.SEZATCPX(EUS) to create one that works for the texts we
>have,  Then in the FTP control statements, used LOCSITE SBDataconn=
>to specify use of the created translation table for the transfer.
> 
Could that not have been done simply by supplying the correct:
(file_system_codepage,network_transfer_codepage)
in the SBDATACONN command:

with no need to "creat a translation table"?

The proper code pages according to:

appear to be "EUS   United States with Euro support 858<->1140"

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Hex (was: Stupid JCL question)

[Michael Oujesky]

At 03:21 PM 12/24/2023, Paul Gilmartin wrote:


On Sun, 24 Dec 2023 14:18:34 -0600, Michael Oujesky wrote:

>Just as an aside, the default EBCDIC to ASCIIi translation table in
>FTP has issues with some special characters.  We used CONVXLAT
>against TCPIP.SEZATCPX(EUS) to create one that works for the texts we
>have,  Then in the FTP control statements, used LOCSITE SBDataconn=
>to specify use of the created translation table for the transfer.
>


Nope, kept it in it's own dataset.


Did you need to create your own table?  Did you need to add it to LNKLST?


Nope, just used EUS from the standard TCPIP library without any 
tweaks.  Just pointed to it's own sequential file, but would probably 
install it via a USERMOD if were going to make it the default text 
translation table.



Do you have unusual code pages?


Nope, just using the original system default.


More easily, I have used SBDATACONN(IBM-1047,ISO8859-1)


More absurdly, in 

When accessing z/OS UNIX files, you must specify the OEMVS311 
translation table ...

"must"?  IOW, IBM's default doesn't work.

--
gil

--
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: Stupid JCL question

[Seymour J Metz]

Yes, but z/OS support multiple code pages. Not even the letters have unique 
encoding.

> That's x'c2  ac'.

That's the UTF-8 encoding of U+00AC; Does Regina support UTF-8 or any other 
encoding of Unicode? What happens if you translate your source to ISO-8859-1 or 
-15?

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


From: IBM Mainframe Discussion List  on behalf of 
Paul Gilmartin <042bfe9c879d-dmarc-requ...@listserv.ua.edu>
Sent: Sunday, December 24, 2023 10:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stupid JCL question

On Sun, 24 Dec 2023 14:15:49 +, Seymour J Metz  wrote:

>No. Code points can be expressed in hex; characters cannot.
>
It depends.  Much IBM literature uses "character" to mean what other cultures
call "octet".  And Unicode documentation shows several representations
for characters, including hex.

>What is 'D0'X? Without knowing the code page, no answer is possible.
>
>This is not limited to EBCDIC on z; n  the PC world, there are two different 
>encodings for logical Not, which is an issue for older implemntations of Rexx; 
>I believe that all of the newest versions recognize both 'AA'X  and 'AC'X.
>
In "regina.pdf", I see: "¬ Logical Not".  That's x'c2  ac'.  But when I 
copy/paste it,
it looks OK on my desktop, but  Regina gets syntax errors.  I prefer 
documentation
with usable examples.

--
gil

--
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: Hex (was: Stupid JCL question)

[Paul Gilmartin]

On Sun, 24 Dec 2023 14:18:34 -0600, Michael Oujesky wrote:

>Just as an aside, the default EBCDIC to ASCIIi translation table in
>FTP has issues with some special characters.  We used CONVXLAT
>against TCPIP.SEZATCPX(EUS) to create one that works for the texts we
>have,  Then in the FTP control statements, used LOCSITE SBDataconn=
>to specify use of the created translation table for the transfer.
>
Did you need to create your own table?  Did you need to add it to LNKLST?
Do you have unusual code pages?
More easily, I have used SBDATACONN(IBM-1047,ISO8859-1)


More absurdly, in 

When accessing z/OS UNIX files, you must specify the OEMVS311 translation 
table ...
"must"?  IOW, IBM's default doesn't work.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Hex (was: Stupid JCL question)

[Michael Oujesky]

Just as an aside, the default EBCDIC to ASCIIi translation table in 
FTP has issues with some special characters.  We used CONVXLAT 
against TCPIP.SEZATCPX(EUS) to create one that works for the texts we 
have,  Then in the FTP control statements, used LOCSITE SBDataconn= 
to specify use of the created translation table for the transfer.


Michael

At 03:42 PM 12/22/2023, Paul Gilmartin wrote:


On Fri, 22 Dec 2023 16:23:31 -0500, Bob Bridges wrote:

>Just to be pedantic, aren't ~all~ characters hex characters?
>
I think the only hex characters are 0-9 and A-F.

> ... That is, they can be expressed in hex.  I suppose (but I'm 
not sure) that "non-hex character" is intended to mean a character 
that can be expressed directly, eg a space can be expressed as 
'40'x or as ' '.  Whereas a tab character in EBCDIC needs to show 
up as '05'x; there's no way to insert it into my data with the  character.

>
It's easy if you use the right editor.

--
gil

--
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: Stupid JCL question

[Paul Gilmartin]

On Sun, 24 Dec 2023 14:15:49 +, Seymour J Metz  wrote:

>No. Code points can be expressed in hex; characters cannot. 
> 
It depends.  Much IBM literature uses "character" to mean what other cultures
call "octet".  And Unicode documentation shows several representations
for characters, including hex.

>What is 'D0'X? Without knowing the code page, no answer is possible.
>
>This is not limited to EBCDIC on z; n  the PC world, there are two different 
>encodings for logical Not, which is an issue for older implemntations of Rexx; 
>I believe that all of the newest versions recognize both 'AA'X  and 'AC'X.
>
In "regina.pdf", I see: "¬ Logical Not".  That's x'c2  ac'.  But when I 
copy/paste it,
it looks OK on my desktop, but  Regina gets syntax errors.  I prefer 
documentation
with usable examples.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Seymour J Metz]

No. Code points can be expressed in hex; characters cannot. 

What is 'D0'X? Without knowing the code page, no answer is possible.

This is not limited to EBCDIC on z; in the PC world, there are two different 
encodings for logical Not, which is an issue for older implemntations of Rexx; 
I believe that all of the newest versions recognize both 'AA'X  and 'AC'X.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר


From: IBM Mainframe Discussion List  on behalf of Bob 
Bridges 
Sent: Friday, December 22, 2023 4:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Stupid JCL question

Just to be pedantic, aren't ~all~ characters hex characters?  That is, they can 
be expressed in hex.  I suppose (but I'm not sure) that "non-hex character" is 
intended to mean a character that can be expressed directly, eg a space can be 
expressed as '40'x or as ' '.  Whereas a tab character in EBCDIC needs to show 
up as '05'x; there's no way to insert it into my data with the  character.

('05'x?  Yeah, I think that’s right.)

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* ...the director and the writers keep changing the script.  The actors will 
do a scene, and the director will say, "OK, that was perfect, but this time, 
Bob, instead of saying 'What's for dinner?' you say, 'Wait a minute!  Benzene 
is actually a hydrocarbon!'  And say it with a Norwegian accent.  Also, we 
think maybe your character should have no arms."  -Dave Barry, describing his 
acting debut in "Dave's World" */

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Paul Gilmartin
Sent: Friday, December 22, 2023 15:48

A likely offender is instream NETDATA, which could have any character, even 
non-hex in any position.  Most characters are non-hex.

--- On Fri, 22 Dec 2023 15:30:03 -0500, Steve Thompson wrote:
>Oh has that come back to byte people!!  (data stream(s) having any hex
>character in any position).

--
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: Stupid JCL question

[Mark Zelden]

MVS 3.8 was just *slightly* earlier than "IF / THEN" conditional JCL existed.  
:-) 

Regards,

Mark
--
Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS
ITIL v3 Foundation Certified
mailto:m...@mzelden.com
Mark's MVS Utilities: http://www.mzelden.com/mvsutil.html


On Fri, 22 Dec 2023 22:28:27 +, Rahim Azizarab  
wrote:

>you can also experiment with this method.  It works on Zos; but I have not 
>tried it on MVS3.8.
>//FULTONMA JOB MSGLEVEL=(1,1)
>//MYPROG PROC P=IEFBR14
>//PSTEP1 EXEC PGM=&P
>// IF (RC LT 4) THEN
>//PSTEP2 EXEC PGM=IEFBR14,PARM='Y'
>// ELSE
>//PSTEP2 EXEC PGM=IEFBR14,PARM='N'
>// ENDIF
>// PEND
>//STEP1 EXEC PROC=MYPROG,P=IEFBR14
>//STEP2 EXEC PROC=MYPROG
>
>
>regards;
>
>Rahim 
>
>
>
>   
>
> 
>
>On Friday, December 22, 2023 at 10:04:29 AM CST, Bob Bridges 
>  wrote:  
> 
> I should know this - I've been using JCL for decades - but I find I'm 
> uncertain about something I haven't done in a while.  I have a production job 
> here that will eventually be rewritten, but for now I'm just going to tell it 
> to execute only the first couple steps.  I had in mind inserting "//" before 
> the part of the JCL that I want to skip.  Very simple.
>
>But wait - does the JCL interpreter discard the rest of the job when it sees 
>that empty '//', or does it interpret the rest as the start of a new job?  
>(Since there's no subsequent JOB statement I'm not terribly worried about it, 
>but it's sloppy; maybe I should just use a COND parm on the JOB card.)  This 
>info is probably in the JCL ref, but I don't immediately see it.
>
>---
>Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
>
>/* "Poor Diogenes; if you knew how to get on with people you wouldn't have to 
>live like that." / "Poor Aristippos; if you knew how to live like this you 
>wouldn't have to get on with people."  -a condensation of their respective 
>schools of thought a few centuries BC */
>
>--
>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: Stupid JCL question

[Steve Beaver]

The worst it’s going to do is look at you 
And not work 

Sent from my iPhone

No one said I could type with one thumb 

> On Dec 22, 2023, at 16:28, Rahim Azizarab 
> <03f036d88eeb-dmarc-requ...@listserv.ua.edu> wrote:
> 
> you can also experiment with this method.  It works on Zos; but I have not 
> tried it on MVS3.8.
> //FULTONMA JOB MSGLEVEL=(1,1)
> //MYPROG PROC P=IEFBR14
> //PSTEP1 EXEC PGM=&P
> // IF (RC LT 4) THEN
> //PSTEP2 EXEC PGM=IEFBR14,PARM='Y'
> // ELSE
> //PSTEP2 EXEC PGM=IEFBR14,PARM='N'
> // ENDIF
> // PEND
> //STEP1 EXEC PROC=MYPROG,P=IEFBR14
> //STEP2 EXEC PROC=MYPROG
> 
> 
> regards;
> 
> Rahim
> 
> 
> 
>   
> 
> 
> 
>On Friday, December 22, 2023 at 10:04:29 AM CST, Bob Bridges 
>  wrote:  
> 
> I should know this - I've been using JCL for decades - but I find I'm 
> uncertain about something I haven't done in a while.  I have a production job 
> here that will eventually be rewritten, but for now I'm just going to tell it 
> to execute only the first couple steps.  I had in mind inserting "//" before 
> the part of the JCL that I want to skip.  Very simple.
> 
> But wait - does the JCL interpreter discard the rest of the job when it sees 
> that empty '//', or does it interpret the rest as the start of a new job?  
> (Since there's no subsequent JOB statement I'm not terribly worried about it, 
> but it's sloppy; maybe I should just use a COND parm on the JOB card.)  This 
> info is probably in the JCL ref, but I don't immediately see it.
> 
> ---
> Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
> 
> /* "Poor Diogenes; if you knew how to get on with people you wouldn't have to 
> live like that." / "Poor Aristippos; if you knew how to live like this you 
> wouldn't have to get on with people."  -a condensation of their respective 
> schools of thought a few centuries BC */
> 
> --
> 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: Stupid JCL question

[Rahim Azizarab]

you can also experiment with this method.  It works on Zos; but I have not 
tried it on MVS3.8.
//FULTONMA JOB MSGLEVEL=(1,1)
//MYPROG PROC P=IEFBR14
//PSTEP1 EXEC PGM=&P
// IF (RC LT 4) THEN
//PSTEP2 EXEC PGM=IEFBR14,PARM='Y'
// ELSE
//PSTEP2 EXEC PGM=IEFBR14,PARM='N'
// ENDIF
// PEND
//STEP1 EXEC PROC=MYPROG,P=IEFBR14
//STEP2 EXEC PROC=MYPROG


regards;

Rahim 



   

 

On Friday, December 22, 2023 at 10:04:29 AM CST, Bob Bridges 
 wrote:  
 
 I should know this - I've been using JCL for decades - but I find I'm 
uncertain about something I haven't done in a while.  I have a production job 
here that will eventually be rewritten, but for now I'm just going to tell it 
to execute only the first couple steps.  I had in mind inserting "//" before 
the part of the JCL that I want to skip.  Very simple.

But wait - does the JCL interpreter discard the rest of the job when it sees 
that empty '//', or does it interpret the rest as the start of a new job?  
(Since there's no subsequent JOB statement I'm not terribly worried about it, 
but it's sloppy; maybe I should just use a COND parm on the JOB card.)  This 
info is probably in the JCL ref, but I don't immediately see it.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* "Poor Diogenes; if you knew how to get on with people you wouldn't have to 
live like that." / "Poor Aristippos; if you knew how to live like this you 
wouldn't have to get on with people."  -a condensation of their respective 
schools of thought a few centuries BC */

--
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: Hex (was: Stupid JCL question)

[Michael Oujesky]

Why am I reminded of the Karate Kid?

Hex-on, hex-off?



At 03:42 PM 12/22/2023, Paul Gilmartin wrote:


On Fri, 22 Dec 2023 16:23:31 -0500, Bob Bridges wrote:

>Just to be pedantic, aren't ~all~ characters hex characters?
>
I think the only hex characters are 0-9 and A-F.

> ... That is, they can be expressed in hex.  I suppose (but I'm 
not sure) that "non-hex character" is intended to mean a character 
that can be expressed directly, eg a space can be expressed as 
'40'x or as ' '.  Whereas a tab character in EBCDIC needs to show 
up as '05'x; there's no way to insert it into my data with the  character.

>
It's easy if you use the right editor.

--
gil

--
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

Hex (was: Stupid JCL question)

[Paul Gilmartin]

On Fri, 22 Dec 2023 16:23:31 -0500, Bob Bridges wrote:

>Just to be pedantic, aren't ~all~ characters hex characters? 
>
I think the only hex characters are 0-9 and A-F.

> ... That is, they can be expressed in hex.  I suppose (but I'm not sure) that 
> "non-hex character" is intended to mean a character that can be expressed 
> directly, eg a space can be expressed as '40'x or as ' '.  Whereas a tab 
> character in EBCDIC needs to show up as '05'x; there's no way to insert it 
> into my data with the  character.
>
It's easy if you use the right editor.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Bob Bridges]

Just to be pedantic, aren't ~all~ characters hex characters?  That is, they can 
be expressed in hex.  I suppose (but I'm not sure) that "non-hex character" is 
intended to mean a character that can be expressed directly, eg a space can be 
expressed as '40'x or as ' '.  Whereas a tab character in EBCDIC needs to show 
up as '05'x; there's no way to insert it into my data with the  character.

('05'x?  Yeah, I think that’s right.)

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* ...the director and the writers keep changing the script.  The actors will 
do a scene, and the director will say, "OK, that was perfect, but this time, 
Bob, instead of saying 'What's for dinner?' you say, 'Wait a minute!  Benzene 
is actually a hydrocarbon!'  And say it with a Norwegian accent.  Also, we 
think maybe your character should have no arms."  -Dave Barry, describing his 
acting debut in "Dave's World" */

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Paul Gilmartin
Sent: Friday, December 22, 2023 15:48

A likely offender is instream NETDATA, which could have any character, even 
non-hex in any position.  Most characters are non-hex.

--- On Fri, 22 Dec 2023 15:30:03 -0500, Steve Thompson wrote:
>Oh has that come back to byte people!!  (data stream(s) having any hex 
>character in any position).

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Paul Gilmartin]

On Fri, 22 Dec 2023 15:30:03 -0500, Steve Thompson wrote:

>"Prudently, you should inspect your JCL to ensure there are no
>happenstance occurrences of your chosen delimiter."
>
>Oh has that come back to byte people!!  (data stream(s) having
>any hex character in any position).
> 
A likely offender is instream NETDATA, which could have any character,
even non-hex in any position.  Most characters are non-hex.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Steve Thompson]

"Prudently, you should inspect your JCL to ensure there are no
happenstance occurrences of your chosen delimiter."


Oh has that come back to byte people!!  (data stream(s) having 
any hex character in any position).


Just say'n

Steve Thompson



On 12/22/2023 2:46 PM, Paul Gilmartin wrote:

On Fri, 22 Dec 2023 17:30:10 +, Sri h Kolusu wrote:

...
Your option works, however, there is another option to make jcl skip steps with 
enclosing the steps as data.

For example, if you had 10 steps and you want only first 6 steps to run then 
simply add //SAVEDD DATA,DLM=## after step 5 and everything else below it 
will be ignored .  It also will give the flexibility of skipping some steps in 
between and run later steps too.


I've used that technique also to introduce free form comments, avoiding
the tedious "//*".

Prudently, you should inspect your JCL to ensure there are no
happenstance occurrences of your chosen delimiter.



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Paul Gilmartin]

On Fri, 22 Dec 2023 17:30:10 +, Sri h Kolusu wrote:
>...
>Your option works, however, there is another option to make jcl skip steps 
>with enclosing the steps as data.
>
>For example, if you had 10 steps and you want only first 6 steps to run then 
>simply add //SAVEDD DATA,DLM=## after step 5 and everything else below it 
>will be ignored .  It also will give the flexibility of skipping some steps in 
>between and run later steps too.
> 
I've used that technique also to introduce free form comments, avoiding
the tedious "//*".

Prudently, you should inspect your JCL to ensure there are no
happenstance occurrences of your chosen delimiter.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Paul Gilmartin]

On Fri, 22 Dec 2023 12:57:00 -0500, Bob Bridges wrote:

>Oh, simply because the whole job is 160-something lines.  One inserted '//' is 
>a lot less risky than editing that many records, that's all.
>
And it's more readily reversible if you want to restore the original job after 
experimenting
and choosing the preferred refactoring of STEP1.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Bob Bridges]

Oh, simply because the whole job is 160-something lines.  One inserted '//' is 
a lot less risky than editing that many records, that's all.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* My own idea, for what it is worth, is that all sadness which is not now 
either arising from the repentance of a concrete sin and hastening towards 
concrete amendment or restitution, or else arising from pity and hastening 
towards active assistance, is simply bad.  -CS Lewis (1898-1963) */

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Jousma, David
Sent: Friday, December 22, 2023 12:49

Ok, so how about the obvious response…… Since you are going to edit the JCL to 
add // or something, why not just comment out or delete the remaining JCL?

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Sri 
h Kolusu
Sent: Friday, December 22, 2023 12:30

Your option works, however, there is another option to make jcl skip steps with 
enclosing the steps as data.

For example, if you had 10 steps and you want only first 6 steps to run then 
simply add //SAVEDD DATA,DLM=## after step 5 and everything else below it 
will be ignored .  It also will give the flexibility of skipping some steps in 
between and run later steps too.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Jousma, David]

Ok, so how about the obvious response…… Since you are going to edit the JCL to 
add // or something, why not just comment out or delete the remaining JCL?

Dave Jousma
Vice President | Director, Technology Engineering





From: IBM Mainframe Discussion List  on behalf of Bob 
Bridges 
Date: Friday, December 22, 2023 at 12:40 PM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Re: Stupid JCL question
Ooh, not bad! At least, it looks not-bad at first blush, though before I 
implement it I guess I'll wait to see what other comments surface here. Thanks, 
Sri. --- Bob Bridges, robhbridges@ gmail. com, cell 336 382-7313 /* Freedom of 
the press


Ooh, not bad!  At least, it looks not-bad at first blush, though before I 
implement it I guess I'll wait to see what other comments surface here.  
Thanks, Sri.



---

Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313



/* Freedom of the press is limited to those who own one.  -Abbott Joseph 
Liebling */



-Original Message-

From: IBM Mainframe Discussion List  On Behalf Of Sri 
h Kolusu

Sent: Friday, December 22, 2023 12:30



Your option works, however, there is another option to make jcl skip steps with 
enclosing the steps as data.



For example, if you had 10 steps and you want only first 6 steps to run then 
simply add //SAVEDD DATA,DLM=## after step 5 and everything else below it 
will be ignored .  It also will give the flexibility of skipping some steps in 
between and run later steps too.



//STEP0100 EXEC PGM=PGM0

//STEP0500 EXEC PGM=PGM4

//STEP0600 EXEC PGM=PGM5

//STEP0700 EXEC PGM=PGM6

//STEP0800 EXEC PGM=PGM7

//STEP0900 EXEC PGM=PGM8



So, from the above example. You code it as follows.



//STEP0100 EXEC PGM=PGM0

//STEP0500 EXEC PGM=PGM4

//SAVEDD DATA,DLM=##

//STEP0600 EXEC PGM=PGM5

//STEP0700 EXEC PGM=PGM6

//STEP0800 EXEC PGM=PGM7

//STEP0900 EXEC PGM=PGM8



For example, if you want to run steps 1 thru 5 and 8 thru 10 you code something 
like this



//STEP0100 EXEC PGM=PGM0

//STEP0500 EXEC PGM=PGM4

//SAVEDD DATA,DLM=##

//STEP0600 EXEC PGM=PGM5

//STEP0700 EXEC PGM=PGM6

##

//STEP0800 EXEC PGM=PGM7

//STEP0900 EXEC PGM=PGM8



--

For IBM-MAIN subscribe / signoff / archive access instructions,

send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Sri h Kolusu]

Bob,

If you did not want to touch the original job, then you can use IEBEDIT which 
lets you edit the job stream. Check out the examples.

https://www.ibm.com/docs/en/zos/2.5.0?topic=utilities-iebedit-edit-job-stream-program

Thanks,
Kolusu

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Bob Bridges]

Ooh, not bad!  At least, it looks not-bad at first blush, though before I 
implement it I guess I'll wait to see what other comments surface here.  
Thanks, Sri.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* Freedom of the press is limited to those who own one.  -Abbott Joseph 
Liebling */

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Sri 
h Kolusu
Sent: Friday, December 22, 2023 12:30

Your option works, however, there is another option to make jcl skip steps with 
enclosing the steps as data.

For example, if you had 10 steps and you want only first 6 steps to run then 
simply add //SAVEDD DATA,DLM=## after step 5 and everything else below it 
will be ignored .  It also will give the flexibility of skipping some steps in 
between and run later steps too.

//STEP0100 EXEC PGM=PGM0
//STEP0500 EXEC PGM=PGM4
//STEP0600 EXEC PGM=PGM5
//STEP0700 EXEC PGM=PGM6
//STEP0800 EXEC PGM=PGM7
//STEP0900 EXEC PGM=PGM8

So, from the above example. You code it as follows.

//STEP0100 EXEC PGM=PGM0
//STEP0500 EXEC PGM=PGM4
//SAVEDD DATA,DLM=##
//STEP0600 EXEC PGM=PGM5
//STEP0700 EXEC PGM=PGM6
//STEP0800 EXEC PGM=PGM7
//STEP0900 EXEC PGM=PGM8

For example, if you want to run steps 1 thru 5 and 8 thru 10 you code something 
like this

//STEP0100 EXEC PGM=PGM0
//STEP0500 EXEC PGM=PGM4
//SAVEDD DATA,DLM=##
//STEP0600 EXEC PGM=PGM5
//STEP0700 EXEC PGM=PGM6
##
//STEP0800 EXEC PGM=PGM7
//STEP0900 EXEC PGM=PGM8

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Bob Bridges]

That's actually how I experimented:  Created a couple of IEFBR14 statements.  
'//' between them caused the second to be discarded; when I added a JOB card 
after the '//', it executed both of them.

I was reluctant to experiment with the real job; it plays with production DSs 
and takes a while to run.  Then "oh, duh!", I thought, and...

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* By 2005 or so, it will be clear that the Internet's impact on the economy 
has been no greater than the fax machine's.  -Paul Krugman, Nobel-prize-winning 
economist in 1998 */

-Original Message-
From: robhbrid...@gmail.com  
Sent: Friday, December 22, 2023 11:20

Never mind - figured it out by experimentation.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of D 
alta
Sent: Friday, December 22, 2023 11:08

 Yes - that will work.  You can also test it using a few IEFBR14 steps.  Insert 
// after the first one and you will see that the subsequent steps will not 
execute.

--- On Friday, December 22, 2023 at 11:04:26 AM EST, Bob Bridges 
 wrote:  
I should know this - I've been using JCL for decades - but I find I'm uncertain 
about something I haven't done in a while.  I have a production job here that 
will eventually be rewritten, but for now I'm just going to tell it to execute 
only the first couple steps.  I had in mind inserting "//" before the part of 
the JCL that I want to skip.  Very simple.

But wait - does the JCL interpreter discard the rest of the job when it sees 
that empty '//', or does it interpret the rest as the start of a new job?  
(Since there's no subsequent JOB statement I'm not terribly worried about it, 
but it's sloppy; maybe I should just use a COND parm on the JOB card.)  This 
info is probably in the JCL ref, but I don't immediately see it.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Sri h Kolusu]

>> I should know this - I've been using JCL for decades - but I find I'm 
>> uncertain about something I haven't done in a while.  I have a production 
>> job here that will eventually be rewritten, but for now I'm just going to 
>> tell it to execute only the first couple steps.  I had in mind inserting 
>> "//" before the part of the JCL that I want to skip.  Very simple.


Bob,

Your option works, however, there is another option to make jcl skip steps with 
enclosing the steps as data.

For example, if you had 10 steps and you want only first 6 steps to run then 
simply add //SAVEDD DATA,DLM=## after step 5 and everything else below it 
will be ignored .  It also will give the flexibility of skipping some steps in 
between and run later steps too.

//STEP0100 EXEC PGM=PGM0

//STEP0200 EXEC PGM=PGM1

//STEP0300 EXEC PGM=PGM2

//STEP0400 EXEC PGM=PGM3

//STEP0500 EXEC PGM=PGM4

//STEP0600 EXEC PGM=PGM5

//STEP0700 EXEC PGM=PGM6

//STEP0800 EXEC PGM=PGM7

//STEP0900 EXEC PGM=PGM8

//STEP1000 EXEC PGM=PGM9

So, from the above example. You code it as follows.

//STEP0100 EXEC PGM=PGM0

//STEP0200 EXEC PGM=PGM1

//STEP0300 EXEC PGM=PGM2

//STEP0400 EXEC PGM=PGM3

//STEP0500 EXEC PGM=PGM4

//SAVEDD DATA,DLM=##
//STEP0600 EXEC PGM=PGM5

//STEP0700 EXEC PGM=PGM6

//STEP0800 EXEC PGM=PGM7

//STEP0900 EXEC PGM=PGM8

//STEP1000 EXEC PGM=PGM9


For example, if you want to run steps 1 thru 5 and 8 thru 10 you code something 
like this

//STEP0100 EXEC PGM=PGM0

//STEP0200 EXEC PGM=PGM1

//STEP0300 EXEC PGM=PGM2

//STEP0400 EXEC PGM=PGM3

//STEP0500 EXEC PGM=PGM4

//SAVEDD DATA,DLM=##
//STEP0600 EXEC PGM=PGM5

//STEP0700 EXEC PGM=PGM6

##
//STEP0800 EXEC PGM=PGM7

//STEP0900 EXEC PGM=PGM8

//STEP1000 EXEC PGM=PGM9


Thanks,
Kolusu



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Paul Gilmartin]

On Fri, 22 Dec 2023 10:36:10 -0600, Michael Oujesky wrote:

>  "/*EOF" works for me and is easy to spot, whereas "// " is
>sometimes easy to miss.
>
Avoid empirical documentation.  There may be cases you don't test.
Submit an RCF.

I believe the behavior was provided to support semi-unattended operations
with a real card reader so the operator needn't press EOF before each job.

But how might it depend on whether the job is submitted via:

o Real card reader?

o Virtual card reader to VM guest?

o SYSOUT=(,INTRDR)?

o TSO SUBMIT?

o ISPF SUBMIT?

o JES2?

o JES3?

o NJE?

o Can it be fooled by::
   - DD DATA,DLM='//'?
   - DD DATA,DLM='xx'?

Could a mischievous programmer read sensitive data in a following job?

I know with the SDSF REXX API, but not the GUI, I can read data
after the '//'.


>At 10:04 AM 12/22/2023, Bob Bridges wrote:
>
>>I should know this - I've been using JCL for decades - but I find
>>I'm uncertain about something I haven't done in a while.  I have a
>>production job here that will eventually be rewritten, but for now
>>I'm just going to tell it to execute only the first couple steps.  I
>>had in mind inserting "//" before the part of the JCL that I want to
>>skip.  Very simple.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Michael Oujesky]

 "/*EOF" works for me and is easy to spot, whereas "// " is 
sometimes easy to miss.


Michael

At 10:04 AM 12/22/2023, Bob Bridges wrote:

I should know this - I've been using JCL for decades - but I find 
I'm uncertain about something I haven't done in a while.  I have a 
production job here that will eventually be rewritten, but for now 
I'm just going to tell it to execute only the first couple steps.  I 
had in mind inserting "//" before the part of the JCL that I want to 
skip.  Very simple.


But wait - does the JCL interpreter discard the rest of the job when 
it sees that empty '//', or does it interpret the rest as the start 
of a new job?  (Since there's no subsequent JOB statement I'm not 
terribly worried about it, but it's sloppy; maybe I should just use 
a COND parm on the JOB card.)  This info is probably in the JCL ref, 
but I don't immediately see it.


---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* "Poor Diogenes; if you knew how to get on with people you 
wouldn't have to live like that." / "Poor Aristippos; if you knew 
how to live like this you wouldn't have to get on with people."  -a 
condensation of their respective schools of thought a few centuries BC */


--
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: Stupid JCL question

[Bob Bridges]

Never mind - figured it out by experimentation.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* Misers are hard to live with, but they make great ancestors.  -from "Money 
Talk", Jan 2009 */

-Original Message-
From: robhbrid...@gmail.com  
Sent: Friday, December 22, 2023 11:04

I should know this - I've been using JCL for decades - but I find I'm uncertain 
about something I haven't done in a while.  I have a production job here that 
will eventually be rewritten, but for now I'm just going to tell it to execute 
only the first couple steps.  I had in mind inserting "//" before the part of 
the JCL that I want to skip.  Very simple.

But wait - does the JCL interpreter discard the rest of the job when it sees 
that empty '//', or does it interpret the rest as the start of a new job?  
(Since there's no subsequent JOB statement I'm not terribly worried about it, 
but it's sloppy; maybe I should just use a COND parm on the JOB card.)  This 
info is probably in the JCL ref, but I don't immediately see it.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Stupid JCL question

[Mike Schwab]

Yes, it will submit starting from the next job card.
Did it for a production worker wanting to just run the start.

On Fri, Dec 22, 2023 at 10:04 AM Bob Bridges  wrote:

> I should know this - I've been using JCL for decades - but I find I'm
> uncertain about something I haven't done in a while.  I have a production
> job here that will eventually be rewritten, but for now I'm just going to
> tell it to execute only the first couple steps.  I had in mind inserting
> "//" before the part of the JCL that I want to skip.  Very simple.
>
> But wait - does the JCL interpreter discard the rest of the job when it
> sees that empty '//', or does it interpret the rest as the start of a new
> job?  (Since there's no subsequent JOB statement I'm not terribly worried
> about it, but it's sloppy; maybe I should just use a COND parm on the JOB
> card.)  This info is probably in the JCL ref, but I don't immediately see
> it.
>
> ---
> Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
>
> /* "Poor Diogenes; if you knew how to get on with people you wouldn't have
> to live like that." / "Poor Aristippos; if you knew how to live like this
> you wouldn't have to get on with people."  -a condensation of their
> respective schools of thought a few centuries BC */
>
> --
> 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: Stupid JCL question

[Robley Lutz]

You’re right. It stops with the //.

From: IBM Mainframe Discussion List  on behalf of Bob 
Bridges 
Sent: Friday, December 22, 2023 11:04:09 AM
To: IBM-MAIN@LISTSERV.UA.EDU 
Subject: Stupid JCL question

I should know this - I've been using JCL for decades - but I find I'm uncertain 
about something I haven't done in a while.  I have a production job here that 
will eventually be rewritten, but for now I'm just going to tell it to execute 
only the first couple steps.  I had in mind inserting "//" before the part of 
the JCL that I want to skip.  Very simple.

But wait - does the JCL interpreter discard the rest of the job when it sees 
that empty '//', or does it interpret the rest as the start of a new job?  
(Since there's no subsequent JOB statement I'm not terribly worried about it, 
but it's sloppy; maybe I should just use a COND parm on the JOB card.)  This 
info is probably in the JCL ref, but I don't immediately see it.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* "Poor Diogenes; if you knew how to get on with people you wouldn't have to 
live like that." / "Poor Aristippos; if you knew how to live like this you 
wouldn't have to get on with people."  -a condensation of their respective 
schools of thought a few centuries BC */

--
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: Stupid JCL question

[D alta]

 Yes - that will work.  You can also test it using a few IEFBR14 steps.  Insert 
// after the first one and you will see that the subsequent steps will not 
execute.
HTH
On Friday, December 22, 2023 at 11:04:26 AM EST, Bob Bridges 
 wrote:  
 
 I should know this - I've been using JCL for decades - but I find I'm 
uncertain about something I haven't done in a while.  I have a production job 
here that will eventually be rewritten, but for now I'm just going to tell it 
to execute only the first couple steps.  I had in mind inserting "//" before 
the part of the JCL that I want to skip.  Very simple.

But wait - does the JCL interpreter discard the rest of the job when it sees 
that empty '//', or does it interpret the rest as the start of a new job?  
(Since there's no subsequent JOB statement I'm not terribly worried about it, 
but it's sloppy; maybe I should just use a COND parm on the JOB card.)  This 
info is probably in the JCL ref, but I don't immediately see it.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* "Poor Diogenes; if you knew how to get on with people you wouldn't have to 
live like that." / "Poor Aristippos; if you knew how to live like this you 
wouldn't have to get on with people."  -a condensation of their respective 
schools of thought a few centuries BC */

--
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: Stupid JCL question

[Michael Watkins]

Since the subsequent JCL statements won't be preceded by a JOB card, they will 
be discarded.

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of Bob 
Bridges
Sent: Friday, December 22, 2023 10:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Stupid JCL question

CAUTION: This email originated from outside of the Texas Comptroller's email 
system.
DO NOT click links or open attachments unless you expect them from the sender 
and know the content is safe.

I should know this - I've been using JCL for decades - but I find I'm uncertain 
about something I haven't done in a while.  I have a production job here that 
will eventually be rewritten, but for now I'm just going to tell it to execute 
only the first couple steps.  I had in mind inserting "//" before the part of 
the JCL that I want to skip.  Very simple.

But wait - does the JCL interpreter discard the rest of the job when it sees 
that empty '//', or does it interpret the rest as the start of a new job?  
(Since there's no subsequent JOB statement I'm not terribly worried about it, 
but it's sloppy; maybe I should just use a COND parm on the JOB card.)  This 
info is probably in the JCL ref, but I don't immediately see it.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* "Poor Diogenes; if you knew how to get on with people you wouldn't have to 
live like that." / "Poor Aristippos; if you knew how to live like this you 
wouldn't have to get on with people."  -a condensation of their respective 
schools of thought a few centuries BC */

--
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

Stupid JCL question

[Bob Bridges]

I should know this - I've been using JCL for decades - but I find I'm uncertain 
about something I haven't done in a while.  I have a production job here that 
will eventually be rewritten, but for now I'm just going to tell it to execute 
only the first couple steps.  I had in mind inserting "//" before the part of 
the JCL that I want to skip.  Very simple.

But wait - does the JCL interpreter discard the rest of the job when it sees 
that empty '//', or does it interpret the rest as the start of a new job?  
(Since there's no subsequent JOB statement I'm not terribly worried about it, 
but it's sloppy; maybe I should just use a COND parm on the JOB card.)  This 
info is probably in the JCL ref, but I don't immediately see it.

---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313

/* "Poor Diogenes; if you knew how to get on with people you wouldn't have to 
live like that." / "Poor Aristippos; if you knew how to live like this you 
wouldn't have to get on with people."  -a condensation of their respective 
schools of thought a few centuries BC */

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN