Re: Words fail me!
Unformatted System Services was used in VTAM to specify the screen and responses to uses to logon to formal VTAM sessions like TSO and CICS. USS was Unix System Services IIRC Matt Hogstrom PGP key 0F143BC1 > On Nov 13, 2021, at 21:02, greg.pr...@optusnet.com.au wrote: > > Way back when (long before UNIX was added to MVS) the network sysprog told > me that USS stood for Unformatted Screen Services. > > Years after that but years (decades?) ago, I noticed that some VTAM books > were talking about UNIX System Services in a context completely unrelated to > UNIX. > > I sent feedback that this was not the correct expansion of USS in this > context. I expect others also did. References to UNIX were soon removed. > > But I wonder if that is why VTAM books talk about Unformatted System Services > now - because they changed UNIX to Unformatted, but not System to Screen. > > Cheers, > Greg > > -- > 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: Words fail me!
Way back when (long before UNIX was added to MVS) the network sysprog told me that USS stood for Unformatted Screen Services. Years after that but years (decades?) ago, I noticed that some VTAM books were talking about UNIX System Services in a context completely unrelated to UNIX. I sent feedback that this was not the correct expansion of USS in this context. I expect others also did. References to UNIX were soon removed. But I wonder if that is why VTAM books talk about Unformatted System Services now - because they changed UNIX to Unformatted, but not System to Screen. Cheers, Greg -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: conditional JCL - Reinvent the wheel?
On Sat, 13 Nov 2021 13:54:15 -0600, Robert Prins wrote: >Replying via the website, so no context, apologies > Replying via the website, with context from clicking on the quotation mark at the upper left of the text composition box, no apologies. >Use "impossible to match" if-then logic, this is what I use in one particular >job to just compile: > >//SET LI=4095 (skip link) >//*SET LI=0 (link if compile is OK) >//* >//IFLINKIF RC <= 4 & RC >= &LI THEN > Your use of "&LI" is not "intended or supported" syntax. The JCL Ref. says: • You can specify symbolic parameters on IF/THEN/ELSE/ENDIF statements provided that they resolve to one of the supported relational-expression keywords. Any other symbolic parameters, even if accepted by the system, are not intended or supported. Refer to “Relational-expression keywords” on page 366. Neither "0" nor "4095" is among the listed “Relational-expression keywords” In old-fashioned JCL, I've used: //STEP0 EXEC PGM=IEFBT14 //STEP1 EXEC whatever,COND=(0,LE) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: conditional JCL - Reinvent the wheel?
Replying via the website, so no context, apologies Use "impossible to match" if-then logic, this is what I use in one particular job to just compile: //SET LI=4095 (skip link) //*SET LI=0 (link if compile is OK) //* //IFLINKIF RC <= 4 & RC >= &LI THEN Robert -- Robert AH Prins robert.ah.prins(a)gmail.com The hitchhiking grandfather - https://prino.neocities.org/ Some REXX code for use on z/OS - https://prino.neocities.org/zOS/zOS-Tools.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
