SYSVIEW Performance Management

 View Only
  • 1.  How to extract CA SYSVIEW IMS Transaction Data

    Posted Feb 19, 2021 05:57 PM
      |   view attached
    I would like to extract all IMS transactions in the history (log) for a given transaction and display the information for the transaction including the USERID and date time.   I am able to do this on an individual basis, one transaction at a time, but would like to extract this information for all the transactions at one time.  I have attached a word document with the steps that I used to find the given transactions one at a time.   I am trying to fulfill a request from computer operations about which user used a specific IMS transaction over a given time.   

    Thank you in advance for any assistance you may be able to offer.

    Patrick

    Attachment(s)

    docx
    imsreport.docx   319 KB 1 version


  • 2.  RE: How to extract CA SYSVIEW IMS Transaction Data

    Broadcom Employee
    Posted Mar 16, 2021 09:39 AM
    Hello Patrick,
    If you are familiar with Report Writer you can use the following //SYSIN DD * cards as an example.

    OPTION(RPTSTAT=YES,RECSTAT=YES,JOBZONE=0WEST,MAXTO=NO)
    FLASHBACK IMS
    FROM 02/20/21 00:00:00
    TO 02/25/21 23:59:59

    END

    RUN

    Your TAPSMF input would be your IMSLOGR.  If you need additional assistance feel free to open a case and note to send it over to me.
     
    Regards,
    Bill


  • 3.  RE: How to extract CA SYSVIEW IMS Transaction Data

    Posted Mar 31, 2021 05:31 PM

    Hi Bill,

    I requested access for the SYSVIEW exit for reading the TAPSMF file, but i am still receiving the error list below.

    JCL
    //REPORT EXEC PGM=XPFRMAIN,REGION=4M
    //ERPTPRM DD DISP=SHR,DSN=SYSNZR.SYSVIEW.SAMPJCL
    //SYSUDUMP DD SYSOUT=*
    //SYSPRINT DD SYSOUT=*
    //TAPSMF DD DISP=SHR,DSN=SYSNZ.SYSVIEW.IMSLOGR.IMTR.NASC.A0001895,
    // SUBSYS=(LOGR,GSVXLGEX)
    //SYSIN DD *
    OPTION(RPTSTAT=YES,RECSTAT=YES,MAXTO=NO)
    SELECT LTERM(*)
    FLASHBACK IMS
    FROM 02/20/21 00:00:00
    TO 03/31/21 23:59:59
    END
    RUN

    Error Messages
    12.12.29 JOB09275 IXG231I IXGCONN REQUEST=CONNECT TO LOG STREAM 569
    12.12.29 JOB09275 GSVX925E TAPSMF IXGCONN CONNECT RC 0008 RS 080B Desc
    569 SYSNZ.SYSVIEW.IMSLOGR.IMTR DID NOT SUCCEED FOR JOB $64159RT. RETURN
    569 CODE: 00000008 REASON CODE: 0000080B DIAG1: 00000000 DIAG2:
    569 00000000 DIAG3: 00000000 DIAG4: 00000000
    JOB09275 IXG504I LOGGER SUBSYSTEM (LOGR) EXIT PROVIDED AN ERROR RETURN 571
    571 DD=TAPSMF EXIT=GSVXLGEX FUNCTION=OPEN RETCODE=00000008
    12.12.29 JOB09275 IEC150I 913-74,IGG0199G,$64159RT,REPORT,TAPSMF 572

    Patrick




  • 4.  RE: How to extract CA SYSVIEW IMS Transaction Data

    Broadcom Employee
    Posted Apr 01, 2021 04:08 AM

    Hi Patrick,
    Please check of the userid running the report is allowed to access/read the logstream datasets.. 

    There is an IEC150I 913-74 message at the bottom. The (S)913 indicates a security violation...
    And according the IEC150I message :

    74
    A security violation occurred when opening a subsystem data set or
    z/OS UNIX file with a DCB. The subsystem was unable to determine the
    user had appropriate access.


    Best regards

    Hennie Hermans



    ------------------------------
    Principal Support Engineer
    CA Technologies, A Broadcom Company
    ------------------------------



  • 5.  RE: How to extract CA SYSVIEW IMS Transaction Data

    Broadcom Employee
    Posted Apr 01, 2021 06:46 AM
    Hello Patrick,

    Regarding the S913-74 abend, it is likely not related to a userid problem. It is much more likely that your batch job ran on a different system than where the log stream is currently connected. 

    For DASD only log streams, you are only permitted to write to and read from a single system at a time. If your log stream has a connection to be written to on system SYSA, but you try to read from it on system SYSB, then you will see abend S913-74.

    If you are running a JES MAS where a job can be submitted and ran on one of many systems, the easiest fix is to code JOBPARM SYSAFF=SYSA on your JCL where SYSA is the system where the log stream is currently connected.

    ------------------------------
    Jason Brosius
    Senior Software Engineer
    Broadcom
    ------------------------------