Re: Infoprint Server, duplex option

See IBM Print Transforms from AFP for Infoprint Server for z/OS Generally the DUPLEX on the OUTPUT JCL card is for AFP output through PSF, but for Infoprint Server there are

Re: PL/I vs. JCL

Charles Mills wrote: >I once had an all-out war (I won! I was the president!) with a tech writer who >insisted that the >documentation should spell out Multiple Virtual Systems on the first reference >to MVS (in technical >documentation for a hardcore mainframe product). My position was that

Re: PL/I vs. JCL

A good tech writer knows what he does not know. Unless he has a primary source for the expansion, he knows the meaning of the word "stet". -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of

Re: PL/I vs. JCL

ObOverloadedAcronym VMS is a failed predecessor to MVT. I used to run PCP and the police didn't mind. DOS runs on S/360 and S/370. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 From: IBM Mainframe Discussion List on behalf of Paul

Re: Abbrev. (was: PL/I vs. JCL)

Now you made me look. It's also Withdraw, Terminate, and Prevent. When will the madness end? :) $P JES2 - Withdraw JES2 from the system $P RMT(n) - Terminate a remote terminal connection $P XEQ - Prevents JES2 and WLM-controlled initiators from selecting work On 10/3/2021 1:44 PM, David

Re: Abbrev. (was: PL/I vs. JCL)

Hi Charles, You said: "... JES P is Purge ..." It is also STOP ($P LOGON) and DRAIN (e.g. $P SPOOL). Regards, David On 2021-10-03 11:17, Charles Mills wrote: There are two different P's. MVS P is stoP. JES P is Purge. Working from (non-parity checked) memory here. Someone will sure hasten to

Re: PL/I vs. JCL

Having wrestled with this issue for decades, I've come to adopt Mainframe as a generic term that most people recognize. (Ignoring the technowienies that debate the term endlessly.) No one argues with the term or even questions it. It covers hardware and software. You can use other terms if you

Re: PL/I vs. JCL

General Tee-esS-Oh is a favorite IT dad joke around here. (Never in front of a waiter.) BTW that dish has nothing to do with the historical general nor with Hunan, his home base. On Sun, Oct 3, 2021 at 10:22 AM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Sun, 3

Re: PL/I vs. JCL

Agreed. Saying MVS makes you look old-fashioned, even though MVS still exists (I guess?) as a component of z/OS. Saying z/OS is limiting. Ditto for the hardware. It is a little wordy to say "I have been writing assembler for the S/360, S370, S/390 and z." (And I guess now Telum?) Does that

Re: PL/I vs. JCL

General Tee-esS-Oh is a favorite IT dad joke around here. (Never in front of a waiter.) BTW that dish has nothing to do with the historical general nor with Hunan, his home base. On Sun, Oct 3, 2021 at 10:22 AM Paul Gilmartin < 000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > On Sun, 3

Re: PL/I vs. JCL

On Sun, 3 Oct 2021 13:48:37 -0400, Phil Smith III wrote: >... >From the USS side, support DD:ddname as a filename and you're good (from C >I'm not actually sure you can avoid supporting that). We have such a use >case and have never had a problem with it. > No. "date >//DD:SYSPRINT" (or many

Re: PL/I vs. JCL

On Sun, 3 Oct 2021 06:58:42 -0700, Charles Mills wrote: > >I once had an all-out war (I won! I was the president!) with a tech writer who >insisted that the documentation should spell out Multiple Virtual Systems on >the first reference to MVS (in technical documentation for a hardcore

Re: PL/I vs. JCL

Charles wrote: >I wrote a (successful!) product that in one very peripheral feature took an >operand that could represent a member name in a default PDS, a dataset name, >or a zFS file name. I differentiated among the three based on length and the >presence or absence of periods and/or slashes.

Re: PL/I vs. JCL

On Sun, 3 Oct 2021 09:37:00 -0700, Skip Robinson wrote: >Newbie auditors are notorious for 'spelling out' abbreviations that over >the decades have become actual names. And yes, idiocy is only one >consequence. The result can be gibberish. > A long time favorite is a local newscaster who read a

Re: PL/I vs. JCL

Hi Skip, You said: "... Nor 'RACF', which everyone says as rack+f. ..." Way back in 2000, when I was working at IBM full-time, I was involved with a few ACF2->RACF conversions. One customer kept driving me crazy by calling IBM's ESM "Ra-KEFF". Regards, David On 2021-10-03 12:37, Skip

Re: PL/I vs. JCL

On 10/3/2021 9:37 AM, Skip Robinson wrote: Another favorite is 'JES'. Nobody spells it out. IBM spells it out in every JES2 manual e.g., https://www.ibm.com/docs/en/zos/2.5.0?topic=jes2-zos-introduction "This information provides an introduction to the job entry subsystem 2 (JES2)."

Re: PL/I vs. JCL

On 10/3/2021 6:58 AM, Charles Mills wrote: I once had an all-out war (I won! I was the president!) with a tech writer who insisted that the documentation should spell out Multiple Virtual Systems on the first reference to MVS (in technical documentation for a hardcore mainframe product). My

Re: PL/I vs. JCL

Newbie auditors are notorious for 'spelling out' abbreviations that over the decades have become actual names. And yes, idiocy is only one consequence. The result can be gibberish. My favorite basket case is 'TSO', which was in ancient history Time Sharing Option. For as long as anyone can

Re: PL/I vs. JCL

On Sun, Oct 3, 2021 at 6:59 AM Charles Mills wrote: > > I don't abbreviate in documentation or discussion. > > Hmmm. I think referring to the console command P resonates with people > more than STOP. I wonder if people do not recognize XMIT better than > TRANSMIT. The goal in documentation

Re: Abbrev. (was: PL/I vs. JCL)

There are two different P's. MVS P is stoP. JES P is Purge. Working from (non-parity checked) memory here. Someone will sure hasten to correct me if I am wrong. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Paul

Re: PL/I vs. JCL

Umm, we can probably blame my memory, not the tech writer, for that one. Charles -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David Spiegel Sent: Sunday, October 3, 2021 7:03 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: PL/I vs.

Abbrev. (was: PL/I vs. JCL)

On Sun, 3 Oct 2021 10:02:46 -0400, David Spiegel wrote: >Hi Charles, >I guess that nobody bothered to tell the tech writer that the "S" in >MVS, is an abbreviation for "Storage". > Decades ago, I learned "Segments", and I've thought that ever since. I may never have uttered it. But, GIYF (sic),

Re: PL/I vs. JCL

Hi Charles, I guess that nobody bothered to tell the tech writer that the "S" in MVS, is an abbreviation for "Storage". Regards, David On 2021-10-03 09:58, Charles Mills wrote: I don't abbreviate in documentation or discussion. Hmmm. I think referring to the console command P resonates with

Re: PL/I vs. JCL

> I don't abbreviate in documentation or discussion. Hmmm. I think referring to the console command P resonates with people more than STOP. I wonder if people do not recognize XMIT better than TRANSMIT. The goal in documentation should be clarity, not pedagogics. I once had an all-out war (I

Re: PL/I vs. JCL

On Sat, 2 Oct 2021 20:56:43 -0700, Charles Mills wrote: >I have no problem with the DD/member ambiguity: > >1. If it's a personal tool and you are happy with the ambiguity, then you >are happy. >2. If it's a "product" then you just document which takes priority. > o z/VM CP and CMS with their