OPS/MVS

 View Only
  • 1.  Are there non-compiled versions of REXX in SYSVIEW?

    Posted Nov 14, 2018 03:37 PM

    We are having a problem at one of our shared customers that is using SYSVIEW.  Our TRX product has a feature that allows mixed RECFM (FB and VB) for SYSPROC and SYSEXEC concatenations handling the sequence number location along the way.  However, in the SYSVIEW  CNM4BREX library, there appear to be members such as DASHBOARD that contain compiled REXX.  Compiled REXX is not currently compatible with our RECFM feature.  My question is whether there is a non-compiled version of these REXX members that the customer could use?



  • 2.  Re: Are there non-compiled versions of REXX in SYSVIEW?
    Best Answer

    Broadcom Employee
    Posted Nov 16, 2018 02:20 PM

    Hi John,

     

    There aren't any a non-compiled versions of the REXX members that you could use.  

    The only option that SYSVIEW provides is the ability to convert the entire library from a Fixed Block dataset to a Variable blocked dataset as compiled REXX execs cannot simply be copied from a RECFM=F data set to a RECFM=V data set. They must be converted..

     

    CA SYSVIEW® Performance Management supplies the following job in SAMPLIB to copy and convert the SYSVIEW REXX execs.

    • REXXFTOV
      This SAMPLIB JCL member invokes the GSVUCFV1 REXX exec described above to copy all REXX execs from a RECFM=F data set to a RECFM=V data set and then to convert any complied REXX execs that were copied by invoking the GSVUCFV2 exec.

     



  • 3.  Re: Are there non-compiled versions of REXX in SYSVIEW?

    Broadcom Employee
    Posted Nov 16, 2018 02:37 PM

    You don't mention the specifics of the problem you are having, but you may want to check out this SYSVIEW Problem record regarding a problem with TRX and SYSVIEW compiled REXX which resulted in a TRX APAR:

    REXX009E DASHBORD FAILED ABEND SC90-099 TRX PRODUCT 



  • 4.  Re: Are there non-compiled versions of REXX in SYSVIEW?

    Posted Nov 16, 2018 05:16 PM

    Thanks for the replies.  The problem was occurring with TRXV5650 applied.  It turns out that the issue was the BLKSIZE. The CNM4BREX data set had a BLKSIZE of 32720 which is equal to TRX maximum leaving no room for adjustments.  A BLKSIZE equal to the SISPEXEC of 27920 works fine.