Space announcement This documentation space provides the same content as before, but the organization of the content has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Implementing the REXX API

The Abend-AID REXX application program interface (API) lets you process REXX EXECs against batch, CICS transaction, and region dumps. You load EXECs from the SYSEXEC DD specified in the Abend-AID viewing server JCL.

The following steps provide the detailed information:

Step1: Modify the viewing server JCL

If you want to be able to execute REXX EXECs from within Abend-AID, include in your viewing server JCL the following DD statement:

//SYSEXEC  DD DSN=compware.kaz170.SKAZREXX

This data set contains the Abend-AID for CICS-supplied REXX sample, SAMPREXX, and the REXX EXECs you write, as described in the Abend-AID for CICS User's guide. The SKAZREXX data set is a fixed block data set with a logical record length of 80. You can concatenate multiple data sets on this DD, but they all must have the same record format and logical record length.

Step 2: Stop and restart the viewing server

After you complete the previous step, you must stop and then restart the viewing server.

Note

You can restrict access to the REXX API by coding the REXX subparameter of the EXTERNAL_SECURITY_FUNCTION_CHECK viewing server configuration parameter. See Parameters to Enable External Security for Viewing Servers for more information.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*