Skip to Main Content
Due to the recent acquisition by IBM, the Adabas & Natural Ideas Portal does not contain ideas from products ApplinX and EntireX any longer. Please refer to the IBM Ideas Portal for these products from now on (IBMid required). Existing content will be migrated during the next few weeks.
Status Released
Workspace Natural for z/OS
Categories Natural (NAT)
Created by Raul Chiriboga
Created on Jan 24, 2024

Identify which skeleton's are used when JCL is generated in SMA


When JCL is generated for a JOB in SMA, we do not know which SKELETON's are being used. If we need to customize the SKELETON to meet customer standards then we have to hunt for the right skeleton that was pulled in. What I ended up doing was adding a comment to each skeleton so that I could see which skeleton was being using when generating the JOBs.


Request: Either add a comment at the top of each Skeleton provided or provide a tool that lets user know what skeletons are used to generate the JOBS.


Here is an example:

//* --------------------------------------------------------------

//* SKELETON: COPY-POE2

//* --------------------------------------------------------------

//* RESTORE DATASET #D-DSN-D(NEW)#

//* FROM DATASET #G-MVS-LIB-GROUP#.#D-VOL-T(OLD)#.CDFILE

//* --------------------------------------------------------------

//COP#S-SEQ# EXEC PGM=ADRDSSU,REGION=6M TAPE

//DUMPFILE DD DISP=SHR,DSN=#G-MVS-LIB-GROUP#.#D-VOL-T(OLD)#.CDFILE TAPE

//SYSPRINT DD SYSOUT=#V-SYSOUT# TAPE

//SYSIN DD * TAPE

RESTORE INDD (DUMPFILE) - TAPE

STORCLAS (SMS) - TAPE

DATASET (INCLUDE (SAG.#D-DSN-T(OLD)#)) - TAPE

RENAMEUNCONDITIONAL ( (SAG.#D-DSN-T(OLD)#, - TAPE

#D-DSN-D(NEW)#) )

Use Case SMA
  • Helen Kretzmann
    Reply
    |
    Nov 22, 2024

    Love it!