CA Endevor

Expand all | Collapse all

LO in batch

  • 1.  LO in batch

    Posted 05-17-2020 07:45 PM
    Anyone have any tricks up their sleeves to extract only output components to a single line like QE LO feature and/or conwrite option components.
    Working on search and replace update component list for output libs and I need to update production CICSLOAD's by element, match their current component list value with their specific production dataset, PRINT scl, API, CSV etc print out the entire component list as if you were doing BX.  or only give you input components.

    LO example:

    GCOS740 LINKMAP SYSLMOD GIO.END.GUNIT.CICSLOAD  went to EBDPA06.CICSLOAD

    and

    GW8L62A3 LINKCICS SYSLMOD VGIO.END.EBDAA07.CICSLOAD  went to CICSP17.CICSLOAD

    I have 4 possible generate stages with upwards of 10 possible CICSLOADs per stage going to 30 possible production CICSLOADs.

    The plan is to take the *loadmod fps from each prod cicsload, build whatever scl will give me the one line containing the current comp list cicsload
    then build the search and replace syntax programmatically.

    Conwrite opt component gives you
    MEMBER NAMES  IN COL 39 FOR 8 BYTES, and DATASET NAME COL 57 FOR 44 BYTES

    It would really nice to have the member element/member name and dastaset on the same line to start, really dont want to have to parse thru the entire comp list for "output section" then "SYSLMOD to find and save dataset name, then write member and output dsname to a 3rd file.

    Thanks,
    Karen


  • 2.  RE: LO in batch

    Posted 05-25-2020 05:42 PM

    Karen,

     

    Did you receive an answer for this?

     

    I am sitting here thinking about this an know that you can run a Batch Component Report from ACMQ that will write an Output to the ACMOUT DD statement could then be a temp dataset.

     

    The input can be like

     

          LIST USED COMPONENTS FOR

             ELEMENT  *          ENVIRONMENT   *

             SYSTEM   *          SUBSYSTEM     *

             TYPE     COBOL*     STAGE NUMBER  *

          OPTIONS

       .

     

    and a line output can be like this

     

    MBR=mbr name    DSN=dataset name.   By the way the "PX - Print component information" from the Batch option 7 Print Element provides this also.

     

    You could then have a REXX or PGM read the output file searching for the DSN's you need. The Member name is on the same line from the ACMOUT or the output of the PX option.

     

    Now having said all of that you could consider use the original API SERVER Routine that was introduced when CA Work Bench came out about 20 years ago.

    It is found on page 2330 of the current guide. This is an excerpt.

     

    JCL to Execute ENTBJAPI-BC1JAAPI

    The JCL in this section is distributed with CA Endevor Software Change Manager as member name BC1JAAPI in the

    iprfx.iqual.CSIQJCL data set. This job shows how to execute program ENTBJAPI, found in member BC1JAAPI. This

    program is distributed as a load module only.

     

    REXX Procedure to Execute ENTBJAPI-ENTBRAPI

    The REXX procedure illustrates how to call the API ENTBJAPI utility program from a REXX procedure. It is distributed

    with CA Endevor Software Change Manager as member name ENTBRAPI in the iprfx.iqual.CSIQCLSO data set.

    The JCL builds the control records required to produce a list of all the systems within an environment. You can modify

    it to produce other types of data supported by the ENTBJAPI utility program. See the ENTBJAPI request record layout

    information in Sample List Inventory Function Call - ENTBJAPI in this section.

     

    If you used the Element Extract AEELM you can basically pull what you would see in a BX in ENDEVOR.

     

    I ran a report and this information came out the "question marks" are where our member/element name is displayed.

     

    COBOL   .????????  SYSLIB

     

    LKED    .???????   SYSLMOD

     

    COBOL   .???????   DBRMLIB

     

    COBOL   .???????   SYSDEBUG

     

    As mentioned before you could write a REXX or Program to extract the information you need and generate the output.

    A great starting for a COBOL program is the age old CCIDRPT1 routine in the CSIQOPTN dataset.

     

    I hope this helps.

     

    Russ Gunter

    CA Broadcom Consultant

    Internal Revenue Service

    Cell: (770) 595-8600

    (TOD) Mon –  Fri  7:45 AM - 4:15 PM Eastern

     

    "Never forget, 'Some gave all, All gave some'"

    "It is amazing what you can accomplish if you do not care who gets the credit", Harry S. Truman

     

    Planned days away, 6/17 &18

     






  • 3.  RE: LO in batch

    Posted 05-26-2020 12:55 PM

    Hi Russ,

    So far, no, I have not raced any other suggestions.  Unfortunately, PX is only input components, basically ACMq in batch, no output libs,  and as you pointed out, AAELM and CSV print component list just parrot out BX report.  So back to square one having to parse out component list, one line at a time until I hit the output section. Perhaps I'll submit an enhancement request.  Thanks for the suggestions.

     

    Karen
    Karen Turner
    Technical Support Sr. Specialist
    Endevor Support

     






  • 4.  RE: LO in batch

    Posted 05-26-2020 02:19 PM
    I have some REXX that reads the reports and removes unwanted lines.
    Interested?

    Bernie

    ------------------------------
    Bernie Beriau
    Endevor Administrator
    CA Technologies/Broadcom
    ------------------------------



  • 5.  RE: LO in batch

    Posted 05-26-2020 03:34 PM

    Karen,

     

    Actually when I was looking at this yesterday I was thinking it would be a good enhancement request.

    I would support it.

     

    Russ Gunter

    CA Broadcom Consultant

    Internal Revenue Service

    Cell: (770) 595-8600

    (TOD) Mon –  Fri  7:45 AM - 4:15 PM Eastern

     

    "Never forget, 'Some gave all, All gave some'"

    "It is amazing what you can accomplish if you do not care who gets the credit", Harry S. Truman

     

    Planned days away, 6/17 &18

     






  • 6.  RE: LO in batch

    Posted 05-26-2020 04:30 PM
    The AEELM approach, found in your CSIQJCL(BC1JAAPI) and using the AEELM option also allows you to select an output format.
    A "C" in column 6 of the AEELM request is a request for "CHANGE DISPLAY FORMAT" which is a single line per relationship.
    A "Table Tool" step could parse the data on each single line for you.

    Have to admit though, having a CSV request for Input and output ACM references would be a better way to go (someday?) .