Just to complement other answers: IEBGENER has nothing to do with it. It
could be IEBCOPY, IDCAMS or your own program.
--
Radoslaw Skorupka
Lodz, Poland
W dniu 11.11.2022 o 19:14, Sasso, Len pisze:
- JES System Symbol (Name of the job - SASSTEST)
- Dynamic System Symbols
Take a look at MOUNTMON
https://ftp.software.ibm.com/storage/tapetool/
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
OA55138: SYSJOBID AND SYSJOBNM INCORRECTLY DOCUMENTED IN THE MVS JCL REFERENCE
V2R3
On page 50 of the MVS JCL Reference V2R3 under section "Using
the SYSUID system symbol" is the following statement referring
to SYSUID, SYSJOBNM and SYSJOBID:
"These symbols are available to JCL and can be used
isn't a system symbol. It's a JES2 symbol.
should work for this purpose, I use it. The other is for JCL
(only, it seems) where usually resolves to "JES2".
sas
On Fri, Nov 11, 2022 at 1:15 PM Sasso, Len <
039db7f8412a-dmarc-requ...@listserv.ua.edu> wrote:
> - JES System Symbol (Name
That's the guide, not the PLM.
SY28-0623, OS/VS2 System Initialization Logic, is the relevant manual for
OS/VS2, and I suspect that there are supplements for MVS/SE and MVS/SP V1.
LY28-1200, MVS/XA MVS/SP-JES3 Version 2 MVS/SP-JES2 Version 2 System
Initialization Logic, is the relevant manual
- JES System Symbol (Name of the job - SASSTEST)
- Dynamic System Symbols
According to IBM, I should be able to use (substitute) the values of these
symbols into the In-Stream Data,
if I code "SYMBOLS=EXECSYS" on the DD Statement.
Below is a PROC and Pend executing IEBGENER and the
Classification: Confidential
Syssym=allow in jesparms?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Sasso, Len
Sent: Friday, November 11, 2022 12:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IEBGENER and JES System Symbol
[CAUTION: This Email is from outside the
