Hi ,
Utility generation using R/C query is really painful , attached the screen prints below.
COMMAND ===>
EXECUTION SPECIFICATIONS:
DESTINATION ===> P ( J - JES, D - Dataset, P - Preview JCL )
OUTPUT JCL DATA SET SPECIFICATIONS:
DATA SET NAME ===> '&hlq.PDS'
MEMBER NAME ===> FUNLOAD1 ( Blank or pattern for member selection list )
VOLUME SERIAL ===> ( If not cataloged )
REPLACE MEMBER ===> Y ( Y - Yes, N - No )
MODEL JCL SPECIFICATIONS:
MODEL LIBRARY ===> '&hlq.CDBAMDL'
MODEL MEMBER ===> ( Blank or pattern for member selection list )
VOLUME SERIAL ===> ( If not cataloged )
JOB CARD SPECIFICATION:
==> //xxxxxA JOB ***,'******',CLASS=X,
==> // MSGLEVEL=(1,1),MSGCLASS=X,NOTIFY=&SYSUID
==>
==>
==>
After the below panel while selecting the model library, its not allowing for any good customization.
MEMBER MASK ===> * (Enter * in any position to denote wildcard search)
-------------------------------------------------------------------------------
S MEMBER DESCRIPTION
_ DMPTICX2 PQC - Sample of advanced model: Copy on tape
_ DMPTICX3 PQC - Sample of advanced model: Copy on Disk (Dyn. SYSCPx)
_ DMPTIFC$ PFC - Informational 'README' member (Use 'B' line command)
_ DMPTIFC1 PFC - Sample of advanced model: CA Fast Check System RI
_ DMPTIFC2 PFC - Sample of advanced model: CA Fast Check Sys/User RI
_ DMPTIFI$ PFI - Informational 'README' member (Use 'B' line command)
_ DMPTIFI1 PFI - Sample of model: Drop/Create IX.
_ DMPTIFL$ PFL - Informational 'README' member (Use 'B' line command)
_ DMPTIFL1 PFL - Sample of model: Load Table - See PFU DMPTIFU1 also
_ DMPTIFL2 PFL - Sample of model: Load Table - See PFU DMPTIFU2 also
_ DMPTIFL3 PFL - Sample of model: Load Table - See PFU DMPTIFU3 also
_ DMPTIFL4 PFL - Sample of model: Load Table - See PFU DMPTIFU3 also
_ DMPTIFL5 PFL - Sample of model: Load Table - See PFU DMPTIFU5 also
_ DMPTIFL6 PFL - Sample of model: Load Table - See PFU DMPTIFU6 also
_ DMPTIFL7 PFL - Sample of model: Load Table - See PFU DMPTIFU7 also
MODEL MEMBER ===> DMPTIFU1 ( Blank or pattern for member selection list )
VOLUME SERIAL ===> ( If not cataloged )
EDIT DATA SET ===> N ( Y - Yes, N - No )
---------------------------------------------------------------------- XXXXX
CMD SYMBOLIC AUTO_REP -------- REPLACEMENT VALUE ---------------------------
_ LOBRLATD Y
_ STEPNAME Y UTIL0000
_ DUUTLVER
_ UTILMD Y MJUTALLU
_ UTILCD Y UD
_ CAUTIL
_ DATEFMTD
_ TIMEFMTD
_ USERID Y XXXXX
_ DUSTATS
After passing through the above panels, Lot of manual effort were required to have the task accomplished to get the work done.
//SYSOUT DD SYSOUT=*
FASTUNLOAD
LOAD-CONTROL NONE
OUTPUT-FORMAT FIXED
IO-BUFFERS 60
INPUT-FORMAT TABLE
SHRLEVEL REFERENCE
EXCP MM
DISPLAY-STATUS %CALC(%ESTROWS/4),ELAPSED
===>>>ERROR - PREVIOUS CARD - %CALC FORMAT ERROR
ESTIMATED-ROWS
Above utility control statements were generated and it doesnot have a good level of customization and added to that how a new user will be able to make changes .
If the user has to make changes why and what is the tool accomplishing to have the work done. Compared to this the IBM admin tool is providing a good level of customization, so the DBA, who is working on it can easlity generate
an utility statement and ready to go instead of maintaing a PDS and a stratergy / model JCL . If CA can work on this to have this addressed, it would be great.#