Re: IBM JCL Expert preview in today's announcement letter

[Mike Schwab]

https://www-356.ibm.com/partnerworld/gsd/solutiondetails.do?solution=37147=true=en

On Wed, Oct 6, 2021 at 6:25 AM Brian Westerman
 wrote:
>
> Do you have the announcement link you can post.  I didn't see any today about 
> a JCL checker.
>
> Brian
>
> --
> 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: IBM JCL Expert preview in today's announcement letter

[Brian Westerman]

Do you have the announcement link you can post.  I didn't see any today about a 
JCL checker.

Brian

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

Re: PL/1 vs JCL (Phonetics)

[Jeremy Nicoll]

On Tue, 5 Oct 2021, at 17:46, Mike Kerford-Byrnes wrote:
> For an alternative phonetic alphabet, this might be of interest (if anyone
> can supply the value for "h")...

There's lots of alternatives!  See: 
https://en.wikipedia.org/wiki/Cockney_Alphabet

-- 
Jeremy Nicoll - my opinions are my own.

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

Re: PL/I vs. JCL

[Bob Bridges]

Gil, did you misunderstand me, or I you?  This ASCII-based IPA ~is~ good for 
"audio" in the sense that it defines unambiguously how one is pronouncing a 
word.  I see "slough" and pronounce it /slu/; someone else sees it and says 
/slaU/.  I pronounce "caught" /cOt/ and "cot" /cat/; some people, I'm told, 
pronounce them the same.

You, OTOH, seem to be talking about "audio" in the sense of talking on the 
phone (for example) and ~spelling~ a word unambiguously, which is a different 
matter.  Maybe I misunderstood.

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

/* Just like genetic diversity, which prevents an epidemic from wiping out a 
whole species at once, diversity in software is a good thing.  -Cliff Stoll, in 
_The Cuckoo's Egg: Tracking a Spy through the Maze of Computer Espionage_ */

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Paul Gilmartin
Sent: Monday, October 4, 2021 21:04

But no good for audio.  If I need to spell something out for local authorities, 
I use the modal NATO codes.  I don't carry all their wallet cards.

--- On Mon, 4 Oct 2021 14:46:50 -0400, Bob Bridges wrote:
>... (There's an ASCII adaptation of the IPA that's actually pretty 
> handy.  Only problem is, no one's ever seen it, except a few of us 
> geeks.  If we all understood that you could have written "/aI Ef ti/", 
> without fear of ambiguity.)

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

Re: PL/I vs. JCL

[Bob Bridges]

Somewhere, perhaps in Civil Air Patrol some decades ago, I got the impression 
that one scheme has indeed become pretty standard, and in particular is used by 
air-traffic control the world over, at least where English is spoken (which is 
mostly).  More recently I've read that it ain't necessarily so.  The American 
police used to have their own scheme, based mostly on given names, but I think 
they've mostly adopted the US military version too.

I speak under correction.

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

/* If you will here stop and ask yourselves why you are not as pious as the 
primitive Christians were, your own heart will tell you, that it is neither 
through ignorance nor inability, but purely because you never thoroughly 
intended it.  -from "A Serious Call to a Devout and Holy Life" by William Law 
(1686-1761) */


-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of CM 
Poncelet
Sent: Monday, October 4, 2021 20:21

able baker charlie dog easy fox

--- On 04/10/2021 15:10, Paul Gilmartin wrote:
> If the newscaster had been an aviator he couldd have said Alfa Foxtrot Tango.
> But an aviator or a mariner wouldn't have needed to.
>
> I believe he said in defense that it appeared in caps in his script.  
> But if that came off a teletype everything would have been caps.
>
> I once recited a serial number to Tech Support using NATO phonetic alphabet.
> She understood immediately; no request for clarification.  Perhaps she 
> was a veteran.  Why can't local emergency services concur on a phonetic 
> alphabet?

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

VSAM RLS False Contention

[Crawford, Robert C.]

Off and on we VSAM RLS false contention plateaus going over IBM's recommended 
.5% rate.  We don't see any kind of triggering behavior in CICS or the CICS 
application.

I would like to at least see the datasets causing the false contention but all 
the false contention buckets in the RMF type 42 subtype 16 records are zero.  
The true contention buckets have values.

It's my understanding the subtype 16 are supposed to have dataset level 
information.  I specified several dataset name levels in RMF VSAMRLS options.  
I also see the same dataset levels in SMS display MONDS commands.

Is it possible I'm missing something that causes DFSSMS to write dataset level 
false contention data?  Am I looking in the wrong place?

Thanks.

Robert Crawford
Mainframe Management
United Services Automobile Association
(210) 913-3822

"Moy glaz! YA ne dolzhen dobavlyat' v nego puding!"
- Tolstoy
Please send requests to mainframe management through our front door at  
go/mfmfrontdoor

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: Tuesday, October 5, 2021 3:33 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: PL/I vs. JCL

And before that MVS-OE., with MVS before Open.


--
Shmuel (Seymour J.) Metz
https://urldefense.com/v3/__http://mason.gmu.edu/*smetz3__;fg!!GryZGb6B1VCs0SfC!TBwvJ8AO8e9VuDJE7lIsISBnAl6KAhctOQOxm3s7DJUmS0PMKUDPz75eQK5LMQqR2TA$
 



From: IBM Mainframe Discussion List  on behalf of 
David Spiegel 
Sent: Tuesday, October 5, 2021 1:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I vs. JCL

Maybe they should've left it as "Open MVS"? (OS/390)

On 2021-10-05 13:08, Tom Brennan wrote:
> I always thought IBM's position on that was pretty silly.  If you make 
> up a new three word name, expect it to quickly be turned into an 
> acronym.  If they didn't want us to reuse an existing little-known 
> acronym they should have named it something else.
>
> On 10/5/2021 9:56 AM, Seymour J Metz wrote:
>>>   USS has always meant Unix System Services.
>>
>>
>> Not unless you have a time machine; Unformatted System Services dates 
>> to the 1970s. Further, the last post here from IBM on the issue said 
>> that USS was not an approved abbreviation for Unix System Services.
>>
>> --
>> Shmuel (Seymour J.) Metz
>> https://urldefense.com/v3/__https://na01.safelinks.protection.outlook
>> .com/?url=http*3A*2F*2Fmason.gmu.edu*2F*smetz3data=04*7C01*7C*7C
>> 66d0453903554718720608d98822bd8d*7C84df9e7fe9f640afb435*7
>> C1*7C0*7C637690505140660718*7CUnknown*7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM
>> DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0*3D*7C1000sdata=Lx
>> w1EM03nZsemipAC1ktZCbgKrL*2BedD7*2BDDlG*2Fiwn*2B8*3Dreserved=0__
>> ;JSUlJX4lJSUlJSUlJSUlJSUlJSUl!!GryZGb6B1VCs0SfC!TBwvJ8AO8e9VuDJE7lIsI
>> SBnAl6KAhctOQOxm3s7DJUmS0PMKUDPz75eQK5LiSU-R24$
>>
>>
>>
>> 
>> From: IBM Mainframe Discussion List  on 
>> behalf of Joe Monk 
>> Sent: Monday, October 4, 2021 9:11 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: PL/I vs. JCL
>>
>> USS is a VTAM term for Unformatted System Services.
>>
>> USS has always meant Unix System Services.
>>
>> Joe
>>
>> On Mon, Oct 4, 2021 at 7:30 PM Mike Schwab 
>> wrote:
>>
>>> U.S.S.  Unformated System Services, until Unix System Services tried 
>>> to take it over.
>>>
>>> On Tue, Oct 5, 2021 at 1:24 AM Paul Gilmartin 
>>> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

 On Mon, 4 Oct 2021 17:35:41 +, Seymour J Metz wrote:

> While TSO does not support unambiguous truncation for command 
> names, it
>>> does for keywords. I don't know about ICCF.
>
 Unambiguous truncation is treacherous.  Addition of new
>>> commands/keywords can break
 legacy art.  For that reason I eschew abbreviations in code and
>>> pedagogy.  The worst
 case occurs when one command is a proper prefix of another command.

 I freely abbreviate on a command line.

 
 On Sat, 2 Oct 2021 20:56:43 -0700, Charles Mills wrote:
> I have no problem with the DD/member ambiguity:
> \edu with the message: INFO IBM-MAIN

 -- gil

 ---
 --- 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
>>>
>>
>> -
>> - For IBM-MAIN subscribe / signoff / archive access instructions, 
>> send email to 

Re: PL/I vs. JCL

[Phil Smith III]

Shmuel wrote:

> IBM has always had a propensity for changing nomenclature, e.g. from Data
Management to Data Administration.

 

Of course.but they didn't change it here: they seemed to decide to use both.
That's even weirder.

 

Changing: zSeries, System z, z Systems, IBM Z, and (sort of) zEnterprise.
That's too many in 20 years.


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

Re: PL/I vs. JCL

[Seymour J Metz]

And before that MVS-OE., with MVS before Open.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
David Spiegel 
Sent: Tuesday, October 5, 2021 1:37 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I vs. JCL

Maybe they should've left it as "Open MVS"? (OS/390)

On 2021-10-05 13:08, Tom Brennan wrote:
> I always thought IBM's position on that was pretty silly.  If you make
> up a new three word name, expect it to quickly be turned into an
> acronym.  If they didn't want us to reuse an existing little-known
> acronym they should have named it something else.
>
> On 10/5/2021 9:56 AM, Seymour J Metz wrote:
>>>   USS has always meant Unix System Services.
>>
>>
>> Not unless you have a time machine; Unformatted System Services dates
>> to the 1970s. Further, the last post here from IBM on the issue said
>> that USS was not an approved abbreviation for Unix System Services.
>>
>> --
>> Shmuel (Seymour J.) Metz
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7C%7C66d0453903554718720608d98822bd8d%7C84df9e7fe9f640afb435%7C1%7C0%7C637690505140660718%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=Lxw1EM03nZsemipAC1ktZCbgKrL%2BedD7%2BDDlG%2Fiwn%2B8%3Dreserved=0
>>
>>
>>
>> 
>> From: IBM Mainframe Discussion List  on
>> behalf of Joe Monk 
>> Sent: Monday, October 4, 2021 9:11 PM
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Subject: Re: PL/I vs. JCL
>>
>> USS is a VTAM term for Unformatted System Services.
>>
>> USS has always meant Unix System Services.
>>
>> Joe
>>
>> On Mon, Oct 4, 2021 at 7:30 PM Mike Schwab 
>> wrote:
>>
>>> U.S.S.  Unformated System Services, until Unix System Services tried
>>> to take it over.
>>>
>>> On Tue, Oct 5, 2021 at 1:24 AM Paul Gilmartin
>>> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:

 On Mon, 4 Oct 2021 17:35:41 +, Seymour J Metz wrote:

> While TSO does not support unambiguous truncation for command
> names, it
>>> does for keywords. I don't know about ICCF.
>
 Unambiguous truncation is treacherous.  Addition of new
>>> commands/keywords can break
 legacy art.  For that reason I eschew abbreviations in code and
>>> pedagogy.  The worst
 case occurs when one command is a proper prefix of another command.

 I freely abbreviate on a command line.

 
 On Sat, 2 Oct 2021 20:56:43 -0700, Charles Mills wrote:
> I have no problem with the DD/member ambiguity:
> \edu with the message: INFO IBM-MAIN

 -- gil

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

--
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: PL/I vs. JCL

[Seymour J Metz]

The title of that bookshelf is z/OS UNIX System Services, not USS.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of Joe 
Monk 
Sent: Tuesday, October 5, 2021 3:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I vs. JCL

What is the title of this book?

https://www.ibm.com/docs/en/zos/2.3.0?topic=zos-unix-system-services

Joe

On Tue, Oct 5, 2021, 13:58 Ed Jaffe  wrote:

> On 10/5/2021 9:56 AM, Seymour J Metz wrote:
> >
> > Further, the last post here from IBM on the issue said that USS was not
> an approved abbreviation for Unix System Services.
>
> Quite so. If you search for "USS" in IBM z/OS 2.5 documentation:
>
> https://www.ibm.com/docs/en/search/USS?scope=SSLTBW_2.5.0
>
> you will find several hits for Unformatted System Services in the
> CommServer books and no hits whatsoever in the z/OS UNIX books.
>
>
> --
> Phoenix Software International
> Edward E. Jaffe
> 831 Parkview Drive North
> El Segundo, CA 90245
> https://secure-web.cisco.com/1sB3lHoqdwC5gG1Vm_3ay2PVQfBDqx_0oPcM2dfJmlwViS5WuBlCUwwNgUAXk4lIGKPiyjDHJvPhdTygn1m8DgKNrY6s9026fjL3wUJJf5w0s7gnJFC29KPC9els0c9be3fHXPGE-Nu8aCdKcV4e_cfXDl9N4U84lBLRYARCmJY5BMNnbrcZ0wFOi-C2Tfm0O3dnNhgUuz6KyaW2fRfxNMKKF_HzZJR-Ai9Nilg0bmomvqZEoFV-4MWyDqz3-RPYIX_XXk0CoDg1fD_75qSynIAHYjALlMMeUGFTTZL1mVtSRznokiVjdQEBF4ez2KQTqF_N-H509WstmgIdmB7kJnc5vyg9Nbck4WCEZxwpRrco71Ha0z8tJeh3n-tXsW7ngFPHVM8nK5Hm1tB-5Ps0tF1ZWwSedCAy9ZXxcO5XykxQf18gN1hgZixbFVEdKb1Sx/https%3A%2F%2Fwww.phoenixsoftware.com%2F
>
>
>
> 
> This e-mail message, including any attachments, appended messages and the
> information contained therein, is for the sole use of the intended
> recipient(s). If you are not an intended recipient or have otherwise
> received this email message in error, any use, dissemination, distribution,
> review, storage or copying of this e-mail message and the information
> contained therein is strictly prohibited. If you are not an intended
> recipient, please contact the sender by reply e-mail and destroy all copies
> of this email message and do not otherwise utilize or retain this email
> message or any or all of the information contained therein. Although this
> email message and any attachments or appended messages are believed to be
> free of any virus or other defect that might affect any computer system
> into
> which it is received and opened, it is the responsibility of the recipient
> to ensure that it is virus free and no responsibility is accepted by the
> sender for any loss or damage arising in any way from its opening or use.
>
> --
> 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: PL/I vs. JCL

[Seymour J Metz]

IBM has always had a propensity for changing nomenclature, e.g. from Data 
Management to Data Administration.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of 
Phil Smith III 
Sent: Tuesday, October 5, 2021 3:10 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I vs. JCL

Joe: Are those eight books the only use of the term in IBM doc? Still
convincing-it's not like it's one isolated RedBook-but perhaps reflecting
that it was perhaps viewed as a mistake (or "Open MVS" was), but one that
was too hard to undo. Guessing we'll never know.



It is curious that "UNIX System Services" is even a term, given that "Open
MVS" and "OMVS" were already around and OMVS is more visible (e.g., you
don't define a "USS segment"). In the Olden Days, I suspect IBM would have
been more careful about such things. Deck chairs at this point.



Also note that those docs talk about "z/OS UNIX", which is yet another
slight variation on the theme! (Yes, probably UNIX System Services is a
subset of z/OS UNIX, but the point is, "USS" stuck.)



...phsiii


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

VOLCAT RACF protection

[Juan Mautalen]

Hi:

Regarding RACF protection of VOLCAT (tape volume catalog), I found the 
following paragraph in IBM DFSMS documentation:

<
In general, tape users do not require any RACF access authority to the VOLCAT. 
During job processing, the updates to the VOLCAT are made by authorized system 
users. However, the VOLCAT still needs a data set profile and should be defined 
with UACC(NONE). Storage administrators using ISMF should have READ access to 
STGADMIN.IGG.LIBRARY and IDCAMS users should have an access level to 
STGADMIN.IGG.LIBRARY appropriate to the function being performed. For the 
required RACF access level when using IDCAMS, refer to "Required Security 
Authorization for VOLCAT Operations" in z/OS DFSMS Access Method Services 
Commands.
>

How do you understand “authorized system users” in this context?
Is it talking about system tasks that don’t even bother to check RACF authority 
to the VOLCAT?

What about, for instance, address spaces like OAM or DFRMM?
Don’t they need any RACF authority over the DATASET profile protecting VOLCAT?

PD: cross posted to the RACF list

Thanks in advance for your help,

Juan G. Mautalen

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

Re: PL/I vs. JCL

[Ron Wells]

Gc28-0629-1  vs2 3.7  11/15/76

Vtam unformatted system services (USS)

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Gibney, Dave
Sent: Tuesday, October 05, 2021 2:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I vs. JCL

** EXTERNAL EMAIL - USE CAUTION **


>From the 1st abstract:
z/OS UNIX System Services (z/OS UNIX)
Is IBM's preferred terminology

> -Original Message-
> From: IBM Mainframe Discussion List  On
> Behalf Of Joe Monk
> Sent: Tuesday, October 05, 2021 12:02 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: PL/I vs. JCL
>
> What is the title of this book?
>
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Furld
> efense.com%2Fv3%2F__https%3A%2F%2Fwww.ibm.com%2Fdocs%2Fen%2Fzos%2F2.3.
> 0%3Ftopdata=04%7C01%7CRon.Wells%40OMF.COM%7C7deb7c4c2bc444fbd11e0
> 8d988334ee9%7C57c0053cb5f84a1e8bb6e8afa09f3b82%7C0%7C0%7C6376905762141
> 73198%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=8Y2OUNnPrMGiP4JS4gv2aNV8qq
> 5uROJAG24eH14Cas4%3Dreserved=0
> ic=zos-unix-system-services__;!!JmPEgBY0HMszNaDT!8tb9V_xzl-
> O2qojJgBt3KsnCxRGI-6He5Al6AhVprIk3GM7yixUGzQiW7wD4mQ$
>
> Joe
>
> On Tue, Oct 5, 2021, 13:58 Ed Jaffe  wrote:
>
> > On 10/5/2021 9:56 AM, Seymour J Metz wrote:
> > >
> > > Further, the last post here from IBM on the issue said that USS
> > > was not
> > an approved abbreviation for Unix System Services.
> >
> > Quite so. If you search for "USS" in IBM z/OS 2.5 documentation:
> >
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Furld
> efense.com%2Fv3%2F__https%3A%2F%2Fwww.ibm.com%2Fdocs%2Fen%2Fsearch%2FU
> SS%3Fsdata=04%7C01%7CRon.Wells%40OMF.COM%7C7deb7c4c2bc444fbd11e08
> d988334ee9%7C57c0053cb5f84a1e8bb6e8afa09f3b82%7C0%7C0%7C63769057621417
> 3198%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBT
> iI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=vZxAo2kzYxrk7XyXyjUOgl1GKJb
> BF2q9Q73K%2F7Wl7TA%3Dreserved=0
> cope=SSLTBW_2.5.0__;!!JmPEgBY0HMszNaDT!8tb9V_xzl-
> O2qojJgBt3KsnCxRGI-6He5Al6AhVprIk3GM7yixUGzQjszvUwCQ$
> >
> > you will find several hits for Unformatted System Services in the
> > CommServer books and no hits whatsoever in the z/OS UNIX books.
> >
> >
> > --
> > Phoenix Software International
> > Edward E. Jaffe
> > 831 Parkview Drive North
> > El Segundo, CA 90245
> >
> https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Furld
> efense.com%2Fv3%2F__https%3A%2F%2Fwww.phoenixsoftware.com%2F__%3B!!JmP
> data=04%7C01%7CRon.Wells%40OMF.COM%7C7deb7c4c2bc444fbd11e08d98833
> 4ee9%7C57c0053cb5f84a1e8bb6e8afa09f3b82%7C0%7C0%7C637690576214173198%7
> CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1
> haWwiLCJXVCI6Mn0%3D%7C1000sdata=W2Dxj74SCrWjSUH0Hpthrc2QhJXw7Ytwj
> VYyER%2FGtT8%3Dreserved=0
> EgBY0HMszNaDT!8tb9V_xzl-O2qojJgBt3KsnCxRGI-
> 6He5Al6AhVprIk3GM7yixUGzQj3ScfQsQ$
> >
> >
> >
> > 
> >  This e-mail message, including any attachments,
> > appended messages and
> the
> > information contained therein, is for the sole use of the intended
> > recipient(s). If you are not an intended recipient or have otherwise
> > received this email message in error, any use, dissemination,
> > distribution, review, storage or copying of this e-mail message and
> > the information contained therein is strictly prohibited. If you are
> > not an intended recipient, please contact the sender by reply e-mail
> > and destroy all copies of this email message and do not otherwise
> > utilize or retain this email message or any or all of the
> > information contained therein. Although this email message and any
> > attachments or appended messages are believed
> to be
> > free of any virus or other defect that might affect any computer
> > system into which it is received and opened, it is the
> > responsibility of the recipient to ensure that it is virus free and
> > no responsibility is accepted by the sender for any loss or damage
> > arising in any way from its opening or use.
> >
> > 
> > -- 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


Email Disclaimer

This E-mail contains confidential information belonging to the sender, which 
may be legally privileged information. This information is intended only for 
the use of the individual or entity addressed above. If you are not 

Re: PL/I vs. JCL

[Phil Smith III]

Joe: Are those eight books the only use of the term in IBM doc? Still
convincing-it's not like it's one isolated RedBook-but perhaps reflecting
that it was perhaps viewed as a mistake (or "Open MVS" was), but one that
was too hard to undo. Guessing we'll never know.

 

It is curious that "UNIX System Services" is even a term, given that "Open
MVS" and "OMVS" were already around and OMVS is more visible (e.g., you
don't define a "USS segment"). In the Olden Days, I suspect IBM would have
been more careful about such things. Deck chairs at this point.

 

Also note that those docs talk about "z/OS UNIX", which is yet another
slight variation on the theme! (Yes, probably UNIX System Services is a
subset of z/OS UNIX, but the point is, "USS" stuck.)

 

...phsiii


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

Re: PL/I vs. JCL

[Gibney, Dave]

From the 1st abstract:
z/OS UNIX System Services (z/OS UNIX)
Is IBM's preferred terminology 

> -Original Message-
> From: IBM Mainframe Discussion List  On
> Behalf Of Joe Monk
> Sent: Tuesday, October 05, 2021 12:02 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: PL/I vs. JCL
> 
> What is the title of this book?
> 
> https://urldefense.com/v3/__https://www.ibm.com/docs/en/zos/2.3.0?top
> ic=zos-unix-system-services__;!!JmPEgBY0HMszNaDT!8tb9V_xzl-
> O2qojJgBt3KsnCxRGI-6He5Al6AhVprIk3GM7yixUGzQiW7wD4mQ$
> 
> Joe
> 
> On Tue, Oct 5, 2021, 13:58 Ed Jaffe  wrote:
> 
> > On 10/5/2021 9:56 AM, Seymour J Metz wrote:
> > >
> > > Further, the last post here from IBM on the issue said that USS was not
> > an approved abbreviation for Unix System Services.
> >
> > Quite so. If you search for "USS" in IBM z/OS 2.5 documentation:
> >
> >
> https://urldefense.com/v3/__https://www.ibm.com/docs/en/search/USS?s
> cope=SSLTBW_2.5.0__;!!JmPEgBY0HMszNaDT!8tb9V_xzl-
> O2qojJgBt3KsnCxRGI-6He5Al6AhVprIk3GM7yixUGzQjszvUwCQ$
> >
> > you will find several hits for Unformatted System Services in the
> > CommServer books and no hits whatsoever in the z/OS UNIX books.
> >
> >
> > --
> > Phoenix Software International
> > Edward E. Jaffe
> > 831 Parkview Drive North
> > El Segundo, CA 90245
> >
> https://urldefense.com/v3/__https://www.phoenixsoftware.com/__;!!JmP
> EgBY0HMszNaDT!8tb9V_xzl-O2qojJgBt3KsnCxRGI-
> 6He5Al6AhVprIk3GM7yixUGzQj3ScfQsQ$
> >
> >
> >
> > 
> > This e-mail message, including any attachments, appended messages and
> the
> > information contained therein, is for the sole use of the intended
> > recipient(s). If you are not an intended recipient or have otherwise
> > received this email message in error, any use, dissemination, distribution,
> > review, storage or copying of this e-mail message and the information
> > contained therein is strictly prohibited. If you are not an intended
> > recipient, please contact the sender by reply e-mail and destroy all copies
> > of this email message and do not otherwise utilize or retain this email
> > message or any or all of the information contained therein. Although this
> > email message and any attachments or appended messages are believed
> to be
> > free of any virus or other defect that might affect any computer system
> > into
> > which it is received and opened, it is the responsibility of the recipient
> > to ensure that it is virus free and no responsibility is accepted by the
> > sender for any loss or damage arising in any way from its opening or use.
> >
> > --
> > 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: PL/I vs. JCL

[Joe Monk]

What is the title of this book?

https://www.ibm.com/docs/en/zos/2.3.0?topic=zos-unix-system-services

Joe

On Tue, Oct 5, 2021, 13:58 Ed Jaffe  wrote:

> On 10/5/2021 9:56 AM, Seymour J Metz wrote:
> >
> > Further, the last post here from IBM on the issue said that USS was not
> an approved abbreviation for Unix System Services.
>
> Quite so. If you search for "USS" in IBM z/OS 2.5 documentation:
>
> https://www.ibm.com/docs/en/search/USS?scope=SSLTBW_2.5.0
>
> you will find several hits for Unformatted System Services in the
> CommServer books and no hits whatsoever in the z/OS UNIX books.
>
>
> --
> Phoenix Software International
> Edward E. Jaffe
> 831 Parkview Drive North
> El Segundo, CA 90245
> https://www.phoenixsoftware.com/
>
>
>
> 
> This e-mail message, including any attachments, appended messages and the
> information contained therein, is for the sole use of the intended
> recipient(s). If you are not an intended recipient or have otherwise
> received this email message in error, any use, dissemination, distribution,
> review, storage or copying of this e-mail message and the information
> contained therein is strictly prohibited. If you are not an intended
> recipient, please contact the sender by reply e-mail and destroy all copies
> of this email message and do not otherwise utilize or retain this email
> message or any or all of the information contained therein. Although this
> email message and any attachments or appended messages are believed to be
> free of any virus or other defect that might affect any computer system
> into
> which it is received and opened, it is the responsibility of the recipient
> to ensure that it is virus free and no responsibility is accepted by the
> sender for any loss or damage arising in any way from its opening or use.
>
> --
> 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: PL/I vs. JCL

[Ed Jaffe]

On 10/5/2021 9:56 AM, Seymour J Metz wrote:


Further, the last post here from IBM on the issue said that USS was not an 
approved abbreviation for Unix System Services.


Quite so. If you search for "USS" in IBM z/OS 2.5 documentation:

https://www.ibm.com/docs/en/search/USS?scope=SSLTBW_2.5.0

you will find several hits for Unformatted System Services in the 
CommServer books and no hits whatsoever in the z/OS UNIX books.



--
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/



This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.

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

Subject: PL/I vs. JCL

[MWW0922/03/M/IBM%IBM]

>alpha bravo charlie delta echo fox-trot golf hotel india juliet kilo
>lima mike november oscar papa quebec romeo sierra tango uniform victor
>whisky x-ray yankee zulu

In the older days there were more amateur radio operators among us. We 
("radio hams") use a somewhat mixed set of phonetics, but not too mixed, 
and slightly different for various users. The result is generally 
understood world wide (by "hams") and has been effective for a LONG time. 
(More than 60 years for me.)

One common variation is the use of country names where it seems 
reasonable. For example, "Norway" instead of "November."

And my description of "radio hams" is primarily for the short wave, long 
distance types of hams. There are other types whose phonetic usage is 
different.

Bill
whiskey 2 whiskey oscar

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

Re: PL/I vs. JCL

[David Spiegel]

Maybe they should've left it as "Open MVS"? (OS/390)

On 2021-10-05 13:08, Tom Brennan wrote:
I always thought IBM's position on that was pretty silly.  If you make 
up a new three word name, expect it to quickly be turned into an 
acronym.  If they didn't want us to reuse an existing little-known 
acronym they should have named it something else.


On 10/5/2021 9:56 AM, Seymour J Metz wrote:

  USS has always meant Unix System Services.



Not unless you have a time machine; Unformatted System Services dates 
to the 1970s. Further, the last post here from IBM on the issue said 
that USS was not an approved abbreviation for Unix System Services.


--
Shmuel (Seymour J.) Metz
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmason.gmu.edu%2F~smetz3data=04%7C01%7C%7C66d0453903554718720608d98822bd8d%7C84df9e7fe9f640afb435%7C1%7C0%7C637690505140660718%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000sdata=Lxw1EM03nZsemipAC1ktZCbgKrL%2BedD7%2BDDlG%2Fiwn%2B8%3Dreserved=0 





From: IBM Mainframe Discussion List  on 
behalf of Joe Monk 

Sent: Monday, October 4, 2021 9:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I vs. JCL

USS is a VTAM term for Unformatted System Services.

USS has always meant Unix System Services.

Joe

On Mon, Oct 4, 2021 at 7:30 PM Mike Schwab  
wrote:



U.S.S.  Unformated System Services, until Unix System Services tried
to take it over.

On Tue, Oct 5, 2021 at 1:24 AM Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> wrote:


On Mon, 4 Oct 2021 17:35:41 +, Seymour J Metz wrote:

While TSO does not support unambiguous truncation for command 
names, it

does for keywords. I don't know about ICCF.



Unambiguous truncation is treacherous.  Addition of new

commands/keywords can break

legacy art.  For that reason I eschew abbreviations in code and

pedagogy.  The worst

case occurs when one command is a proper prefix of another command.

I freely abbreviate on a command line.


On Sat, 2 Oct 2021 20:56:43 -0700, Charles Mills wrote:

I have no problem with the DD/member ambiguity:
\edu with the message: INFO IBM-MAIN


-- gil

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



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


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

Re: PL/I vs. JCL

[Tom Brennan]

I always thought IBM's position on that was pretty silly.  If you make 
up a new three word name, expect it to quickly be turned into an 
acronym.  If they didn't want us to reuse an existing little-known 
acronym they should have named it something else.


On 10/5/2021 9:56 AM, Seymour J Metz wrote:

  USS has always meant Unix System Services.



Not unless you have a time machine; Unformatted System Services dates to the 
1970s. Further, the last post here from IBM on the issue said that USS was not 
an approved abbreviation for Unix System Services.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of Joe Monk 

Sent: Monday, October 4, 2021 9:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I vs. JCL

USS is a VTAM term for Unformatted System Services.

USS has always meant Unix System Services.

Joe

On Mon, Oct 4, 2021 at 7:30 PM Mike Schwab  wrote:


U.S.S.  Unformated System Services, until Unix System Services tried
to take it over.

On Tue, Oct 5, 2021 at 1:24 AM Paul Gilmartin
<000433f07816-dmarc-requ...@listserv.ua.edu> wrote:


On Mon, 4 Oct 2021 17:35:41 +, Seymour J Metz wrote:


While TSO does not support unambiguous truncation for command names, it

does for keywords. I don't know about ICCF.



Unambiguous truncation is treacherous.  Addition of new

commands/keywords can break

legacy art.  For that reason I eschew abbreviations in code and

pedagogy.  The worst

case occurs when one command is a proper prefix of another command.

I freely abbreviate on a command line.


On Sat, 2 Oct 2021 20:56:43 -0700, Charles Mills wrote:

I have no problem with the DD/member ambiguity:
\edu with the message: INFO IBM-MAIN


-- gil

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



--
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: PL/I vs. JCL

[Seymour J Metz]

>  USS has always meant Unix System Services.


Not unless you have a time machine; Unformatted System Services dates to the 
1970s. Further, the last post here from IBM on the issue said that USS was not 
an approved abbreviation for Unix System Services.

--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3



From: IBM Mainframe Discussion List  on behalf of Joe 
Monk 
Sent: Monday, October 4, 2021 9:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: PL/I vs. JCL

USS is a VTAM term for Unformatted System Services.

USS has always meant Unix System Services.

Joe

On Mon, Oct 4, 2021 at 7:30 PM Mike Schwab  wrote:

> U.S.S.  Unformated System Services, until Unix System Services tried
> to take it over.
>
> On Tue, Oct 5, 2021 at 1:24 AM Paul Gilmartin
> <000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> >
> > On Mon, 4 Oct 2021 17:35:41 +, Seymour J Metz wrote:
> >
> > >While TSO does not support unambiguous truncation for command names, it
> does for keywords. I don't know about ICCF.
> > >
> > Unambiguous truncation is treacherous.  Addition of new
> commands/keywords can break
> > legacy art.  For that reason I eschew abbreviations in code and
> pedagogy.  The worst
> > case occurs when one command is a proper prefix of another command.
> >
> > I freely abbreviate on a command line.
> >
> > 
> > On Sat, 2 Oct 2021 20:56:43 -0700, Charles Mills wrote:
> > >I have no problem with the DD/member ambiguity:
> > >\edu with the message: INFO IBM-MAIN
> >
> > -- gil
> >
> > --
> > 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
>

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

PL/1 vs JCL (Phonetics)

[Mike Kerford-Byrnes]

For an alternative phonetic alphabet, this might be of interest (if anyone
can supply the value for "h")...

 

A for 'orses

B for pork

C for thighlanders (Seaforth Highlanders - British Army regiment)

D for dumb

E for strain

F or vescent

G for police

H ???  (I have never managed to work this one out)

I for Novello

J for Orange

K for ancis (Kay Francis - American actress, died 1960s)

L for leather

M for sis

N for mation

O for the hills

P for relief

Q for a bus

R for minute

S for anto

T for two

U for mism

V for la France

W for a dollar

X for breakfast

Y for heaven's sake

Z for effect 

 

MKB

 


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

Re: Mainframe ransomware solution

[kekronbekron]

Perhaps Infinidat storage has ransomware-specific recovery too.

- KB

‐‐‐ Original Message ‐‐‐

On Tuesday, October 5th, 2021 at 8:33 PM, Charles Mills  
wrote:

> Also make sure that your decryption keys for the backed up data are stored 
> somewhere off mainframe and air-gapped from the Internet. A backup won't do 
> you much good if you can't decrypt it.
>
> Charles
>
> -Original Message-
>
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Bfishing
>
> Sent: Tuesday, October 5, 2021 7:14 AM
>
> To: IBM-MAIN@LISTSERV.UA.EDU
>
> Subject: Re: Mainframe ransomware solution
>
> As already mentioned, having defined copies of your data over time helps.
>
> Just make sure your recovery point and time are understood since the real
>
> tricky part is going back to a point before you were hacked.
>
> IBM's Safeguarded Copy will give you the isolated copies of data over time.
>
> Just make sure you pick the correct one.
>
> https://www.ibm.com/downloads/cas/BNZGVJKD
>
> On Tue, Oct 5, 2021 at 9:24 AM Tommy Tsui tommyt...@gmail.com wrote:
>
> > > Hi
> >
> > Any shop implement mainframe ransomware solution can share? IBM seems has
> >
> > cyber vault to handle this. Is there any other solution available ?
> >
> > Thanks for sharing
>
> 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: Infoprint Server, duplex option

[Roger Bolan]

Yes.  You can use the DUPLEX option on the OUTPUT JCL statement with
Printway Extended as long as you have set the correct values in
duplexes-supported in your printer definition.  If you tell Printway what
kind of duplexing your printer supports, then it can do it.
See
https://www.ibm.com/docs/en/zos/2.5.0?topic=ppdip-validating-that-data-sets-can-print-as-requested-basic-extended-mode#pwlimit

On Mon, Oct 4, 2021 at 8:29 PM Frank Swarbrick 
wrote:

> Hi Roger,
>
> We do currently use PCL in document-header parameters to specify duplex,
> font, orientation, etc.  That means we have at least 12 different printer
> definitions for each printer.  Allowing dynamic specification of the duplex
> parameter would allow use to cut this down to 4, I think (80 char portrait,
> 132 char portrait, 132 char landscape and 176 char landscape, I think.)
> I was wondering if we could eliminate at least the duplex PCL code and
> specify DUPLEX in the JCL.
>
> We do use some transforms, but we don't use them for simple text output.
>
> 
> From: IBM Mainframe Discussion List  on behalf
> of Roger Bolan 
> Sent: Sunday, October 3, 2021 11:18 PM
> To: IBM-MAIN@LISTSERV.UA.EDU 
> Subject: Re: Infoprint Server, duplex option
>
> See IBM Print Transforms from AFP for Infoprint Server for z/OS
> <
> http://publibfp.boulder.ibm.com/epubs/pdf/aokfa102.pdf?mhsrc=ibmsearch_a=%22infoprint%20Server%22%20duplex%20afpxpcl
> >
> Generally the DUPLEX on the OUTPUT JCL card is for AFP output through PSF,
> but for Infoprint Server there are associated products that transform AFP
> documents into PCL, Postscript, or PDF and some of these can use the DUPLEX
> attribute.  For Infoprint Server it is also possible to define a
> document-header value which can be a string of PCL/PJL commands understood
> by most printers. See PCL 5 Printer Language Technical Quick Reference
> Guide (hp.com) 
> If your printer accepts the PCL header and can do duplex, you can set the
> control for duplex in the document-header of a printer definition for the
> printer.
> --Roger
>
>
> On Thu, Sep 30, 2021 at 5:23 PM Frank Swarbrick <
> frank.swarbr...@outlook.com>
> wrote:
>
> > Does anyone happen to know if non-PSF print jobs (specifically, LPR or
> > IPP) support the use of the DUPLEX parameter on the OUTPUT JCL statement?
> > I've tried it with an IP Printway LPR printer definition, but it doesn't
> > seem to have any effect.  The documentation leads me to think it might
> only
> > be supported for PSF printers, but it's really not clear.
> >
> > --
> > 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
>

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

Re: Mainframe ransomware solution

[Charles Mills]

Also make sure that your decryption keys for the backed up data are stored 
somewhere off mainframe and air-gapped from the Internet. A backup won't do you 
much good if you can't decrypt it.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Bfishing
Sent: Tuesday, October 5, 2021 7:14 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mainframe ransomware solution

As already mentioned, having defined copies of your data over time helps.
Just make sure your recovery point and time are understood since the real
tricky part is going back to a point before you were hacked.

IBM's Safeguarded Copy will give you the isolated copies of data over time.
Just make sure you pick the correct one.
https://www.ibm.com/downloads/cas/BNZGVJKD

On Tue, Oct 5, 2021 at 9:24 AM Tommy Tsui  wrote:

> >
> > Hi
>
>  Any shop implement mainframe ransomware solution can share? IBM seems has
> cyber vault to handle this. Is there any other solution available ?
> Thanks for sharing

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

Re: Error running RCNVTCAT

[Paul Gilmartin]

On Tue, 5 Oct 2021 20:16:40 +0700, Robin Atwood wrote:

>The "outtrap" function is a TSO/E extension. You should execute the exec under 
>the TMP (IKJEFT01).
> 
Therre's YA argument here for ANSI Rexx with its standard redirections.

-- gil

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

Re: Error running RCNVTCAT

[Mark Jacobs]

Thanks all. I did just that, executed it under TSO. Worked fine.

Mark Jacobs

Sent from ProtonMail, Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com

‐‐‐ Original Message ‐‐‐

On Tuesday, October 5th, 2021 at 10:09 AM, Richards, Robert B. (CTR) 
<01c91f408b9e-dmarc-requ...@listserv.ua.edu> wrote:

> Thanks for the info, Robin!
>
> I never thought about it because it runs so quick (< 30 secs) that I always 
> run it from ISPF Option 6, watch its progress and let the code place me in 
> EDIT on the PDS immediately.
>
> Bob
>
> -Original Message-
>
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of 
> Robin Atwood
>
> Sent: Tuesday, October 5, 2021 9:17 AM
>
> To: IBM-MAIN@LISTSERV.UA.EDU
>
> Subject: Re: Error running RCNVTCAT
>
> The "outtrap" function is a TSO/E extension. You should execute the exec 
> under the TMP (IKJEFT01).
>
> Robin
>
> -Original Message-
>
> From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On Behalf Of 
> Mark Jacobs
>
> Sent: 05 October 2021 19:29
>
> To: IBM-MAIN@LISTSERV.UA.EDU
>
> Subject: Error running RCNVTCAT
>
> It's my first time executing RCNVTCAT which I obtained from file 542 on the 
> CBTTAPE. Getting this error; IRX0043I Error running RCNVTCAT, line 1016: 
> Routine not found
>
> In SYSTSPRT there are these two lines
>
> 1016 +++ xx=outtrap('junk.','') / I don't care */
>
> 209 +++ If (DsExist("'"cat.1"'") > 4)
>
> Is this a stupid-user-error, or something else? It's being executed using a 
> modified copy of the JCL in the PDS.
>
> //RCNVTCAT EXEC PGM=IRXJCL,COND=EVEN,
>
> // PARM='RCNVTCAT CATALOG.Z22Z.MASTER'
>
> //SYSEXEC DD DISP=SHR,DSN=SY010A.V501.FILE542.PDS
>
> Mark Jacobs
>
> Sent from ProtonMail, Swiss-based encrypted email.
>
> GPG Public Key - 
> https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
>
> -
>
> 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

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

Re: Mainframe ransomware solution

[Bfishing]

As already mentioned, having defined copies of your data over time helps.
Just make sure your recovery point and time are understood since the real
tricky part is going back to a point before you were hacked.

IBM's Safeguarded Copy will give you the isolated copies of data over time.
Just make sure you pick the correct one.
https://www.ibm.com/downloads/cas/BNZGVJKD

On Tue, Oct 5, 2021 at 9:24 AM Tommy Tsui  wrote:

> >
> > Hi
>
>  Any shop implement mainframe ransomware solution can share? IBM seems has
> cyber vault to handle this. Is there any other solution available ?
> Thanks for sharing
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>


-- 

><º>`·.¸¸´¯`·.¸.·´¯`·...¸>(((º>
.·´¯`·.><º>`·.¸¸.·´¯`·.¸.·´¯`·...¸><º>

<>< Go fishing ><>

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

Re: Error running RCNVTCAT

[Richards, Robert B. (CTR)]

Thanks for the info, Robin! 

I never thought about it because it runs so quick (< 30 secs) that I always run 
it from ISPF Option 6, watch its progress and let the code place me in EDIT on 
the PDS immediately.

Bob

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Robin Atwood
Sent: Tuesday, October 5, 2021 9:17 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Error running RCNVTCAT

The "outtrap" function is a TSO/E extension. You should execute the exec under 
the TMP (IKJEFT01).

Robin

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Mark Jacobs
Sent: 05 October 2021 19:29
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Error running RCNVTCAT

It's my first time executing RCNVTCAT which I obtained from file 542 on the 
CBTTAPE. Getting this error; IRX0043I Error running RCNVTCAT, line 1016: 
Routine not found

In SYSTSPRT there are these two lines
1016 +++ xx=outtrap('junk.','*') /* I don't care */
209 +++ If (DsExist("'"cat.1"'") > 4)

Is this a stupid-user-error, or something else? It's being executed using a 
modified copy of the JCL in the PDS.

//RCNVTCAT EXEC PGM=IRXJCL,COND=EVEN,
// PARM='RCNVTCAT CATALOG.Z22Z.MASTER'
//SYSEXEC DD DISP=SHR,DSN=SY010A.V501.FILE542.PDS

Mark Jacobs

Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com

--
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: Mainframe ransomware solution

[Rupert Reynolds]

Shops I've worked at have mostly relied on the general protections against
intrusion, plus good (frequently tested) backup copies.

I'd go further and say that a proper archive (write once, can't update) is
essential if you rely on old data.

Roops

On Tue., Oct. 5, 2021, 14:24 Tommy Tsui,  wrote:

> >
> > Hi
>
>  Any shop implement mainframe ransomware solution can share? IBM seems has
> cyber vault to handle this. Is there any other solution available ?
> Thanks for sharing
>
> --
> 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

IBM JCL Expert preview in today's announcement letter

[Pommier, Rex]

Hi list,

Does anybody have any insight they could share about the announcement IBM made 
today about a JCL checker they're planning on releasing Q1 2022?  I'm curious 
if this is something IBM is developing or if they have partnered with one of 
the third party JCL checkers and will be reselling it.  

Thanks,

Rex

--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.


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

Mainframe ransomware solution

[Tommy Tsui]

>
> Hi

 Any shop implement mainframe ransomware solution can share? IBM seems has
cyber vault to handle this. Is there any other solution available ?
Thanks for sharing

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

Re: Error running RCNVTCAT

[Robin Atwood]

The "outtrap" function is a TSO/E extension. You should execute the exec under 
the TMP (IKJEFT01).

Robin

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Mark Jacobs
Sent: 05 October 2021 19:29
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Error running RCNVTCAT

It's my first time executing RCNVTCAT which I obtained from file 542 on the 
CBTTAPE. Getting this error; IRX0043I Error running RCNVTCAT, line 1016: 
Routine not found

In SYSTSPRT there are these two lines
1016 +++ xx=outtrap('junk.','*') /* I don't care */
209 +++ If (DsExist("'"cat.1"'") > 4)

Is this a stupid-user-error, or something else? It's being executed using a 
modified copy of the JCL in the PDS.

//RCNVTCAT EXEC PGM=IRXJCL,COND=EVEN,
// PARM='RCNVTCAT CATALOG.Z22Z.MASTER'
//SYSEXEC DD DISP=SHR,DSN=SY010A.V501.FILE542.PDS

Mark Jacobs

Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com

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

Error running RCNVTCAT

[Mark Jacobs]

It's my first time executing RCNVTCAT which I obtained from file 542 on the 
CBTTAPE. Getting this error;
IRX0043I Error running RCNVTCAT, line 1016: Routine not found

In SYSTSPRT there are these two lines
1016 +++ xx=outtrap('junk.','*') /* I don't care */
209 +++ If (DsExist("'"cat.1"'") > 4)

Is this a stupid-user-error, or something else? It's being executed using a 
modified copy of the JCL in the PDS.

//RCNVTCAT EXEC PGM=IRXJCL,COND=EVEN,
// PARM='RCNVTCAT CATALOG.Z22Z.MASTER'
//SYSEXEC DD DISP=SHR,DSN=SY010A.V501.FILE542.PDS

Mark Jacobs

Sent from [ProtonMail](https://protonmail.com), Swiss-based encrypted email.

GPG Public Key - 
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com

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