Nothing Special   »   [go: up one dir, main page]
Scribd Logo
Upload

Welcome to Scribd!

  • 9 views

    Mainframe KA

    Uploaded by

    Ilyasuddin Shaikh
    The document provides instructions for printing Control-D reports to separate sequential files using a print mission with the SEQL-FILE category. It explains that each report should be set to Wait Print using the same mission, and the CTDX005 exit must be customized. This exit will generate a unique dataset name for each report based on autoedit variables like %FORM%, %USER%, etc. So each report can be printed to its own sequential file using a customized dataset name format.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Mainframe KA

    Uploaded by

    Ilyasuddin Shaikh
    9 views3 pages
    The document provides instructions for printing Control-D reports to separate sequential files using a print mission with the SEQL-FILE category. It explains that each report should be set to Wait Print using the same mission, and the CTDX005 exit must be customized. This exit will generate a unique dataset name for each report based on autoedit variables like %FORM%, %USER%, etc. So each report can be printed to its own sequential file using a customized dataset name format.

    Original Description:

    Original Title

    mainframe KA

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document provides instructions for printing Control-D reports to separate sequential files using a print mission with the SEQL-FILE category. It explains that each report should be set to Wait Print using the same mission, and the CTDX005 exit must be customized. This exit will generate a unique dataset name for each report based on autoedit variables like %FORM%, %USER%, etc. So each report can be printed to its own sequential file using a customized dataset name format.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    9 views3 pages

    Mainframe KA

    Uploaded by

    Ilyasuddin Shaikh
    The document provides instructions for printing Control-D reports to separate sequential files using a print mission with the SEQL-FILE category. It explains that each report should be set to Wait Print using the same mission, and the CTDX005 exit must be customized. This exit will generate a unique dataset name for each report based on autoedit variables like %FORM%, %USER%, etc. So each report can be printed to its own sequential file using a customized dataset name format.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    How to print Control-D reports to seperate files one per report

    I have 400 reports that need to be printed to 400 sequential files. I know I can use category
    SEQL-FILE in a print mission but how do I get a unique dataset for each report.

    each report should be set to Wait Print using the same mission that has the SEQL-FILE as the
    category. You then need to customize exit CTDX005. This exit looks at the dataset name for
    each report created and if the name has not changed then the existing dataset is used.
    likewise of the name has changed then a new dataset is opened.

    The name is controlled by parameter DSN in the exit. you can set this parameter to be any
    valid dataset name and you can use certain autoedit variables in the name. The variables are:

    %FORM% The report form. The first four characters are used to construct the data set name.

    %USER% The recipient of the report.

    %REPORT% The report name. The first eight characters are used to construct the data set
    name.

    %REMARK% The report remark. The first eight characters are used to construct the data set
    name.

    %JOBNAME% The name of the job that produced the report.

    %EXTWTR% The related external writer name.

    %ODATE% The originating date of the report.

    %DATE% The current date in format yymmdd

    %TIME% The current time in format hhmmss.

    So for example, if you want the dataset name to include a high level qualifier of IOA, the user
    name, jobname and first 8 characters of the report name you would code

    DSN=IOA.%USER%.%JOBNAME%.%REPORT%.D%DATE%.T%TIME%

    For further explanation and examples, please refer to the Incontrol for OS/390 Administrators
    Guide in chapter 4 under section Printing to a file.

    NOTE: you cannot write to a GDG using CTDX005


    What version of JAVA should be used with Control-D/WebAccess Server?
    Why do we need JAVA for? 

    14/09/2022 The latest JAVA version is JAVA 8.


    https://www.java.com/fr/

    1) The minimum JAVA version for 9.0.xx up to 9.0.21 is Java 1.8

    2) CONTROL-D/WebAccess features that use the JAVA code:

    On the WebAccess server side:


    - for the installation process
    - for the Digital Signature feature
    - for some transformation process
    NOTE: Up to version 9.0.20 we use the Java Runtime Environment from the installation
    file in folder /JRE

    On the user Workstation:


    - for the Logical View feature only.
    NOTE: If the end user does NOT use the Logical View feature then JAVA is NOT required.

    3) How to display the JAVA version?

    In a DOS window, run the command java -version

    Sample with the JAVA version from the CONTROL-D/WebAccess distribution in /JRE
    folder:

    Switch to CONTROL-D/WebAccess /JRE folder containing the JAVA distributed by BMC.


    C:\Program Files\BMC Software\Control-D\wa_9.0.20.000\JRE\bin>java -version
    java version "1.8.0_112"
    Java(TM) SE Runtime Environment (build 1.8.0_112-b15)
    Java HotSpot(TM) 64-Bit Server VM (build 25.112-b15, mixed mode)

    NOTES:  
    - JRE stand for Java Runtime Environment.
    - Starting with CONTROL-D/WebAccess 9.0.21 the /JRE folder will not be distributed
    anymore.
    The customer will have to install JAVA or JRE on the CONTROL-D/WebAccess server and
    on all workstation that  will use the Logical View.
    How can I access a new installed IOA Main Menu using a CLIST?

    Do the following:
    1. Locate your &ILPREFA.CLIST library.
    2. Select member: IOASTART
    3. Make a copy of the IOASTART member. (you don't want to update the vanilla member
    IOASTART)
    4. Update the following line in your new IOASTARTx member.
             PROC 0 DEBUG ILPREFA() TRANID(IALL)
    5. To verify what your ILPREFA is, do the following:
             From your &ILPREFA.PARM library, member DEFPARM
             Look for: %ILPREFA%=BMCIOA.Q800I
             In this example, you would update the IOASTARTx member to look like the following:
     
     PROC 0 DEBUG ILPREFA(bmcioa.q800i) TRANID(IALL)
    6. Exec your new member.
    7. Your IOA Main Menu will appear.

    You might also like