Using RMM TSO subcommands with System REXX

RMM TSO subcommands can be issued by System REXX as long as the target System REXX environment is TSO=YES (No testing has been done with TSO=NO). You should put the REXX exec containing the RMM TSO subcommands in the library supported by System REXX, currently SYS1.SAXREXEC. You can execute any system REXX exec using the operator command "F AXR,rexx_name" from a console. Just as with regular REXX, if your system REXX exec sets the REXX variable SYSAUTH.EDGDATE, the RMM subcommand processing creates REXX variables as expected. If SYSAUTH.EDGDATE is not set, RMM subcommand processing results in no REXX variables being created and the resulting line command output is issued to the console.

For example:

/* REXX */
 sysauth.edgdate = 'AMERICAN'
 "RMM SV OWNER(*)"
 say 'command = RMM SV OWNER(*)'
 say 'num vols = ' edg@vol.0
 say 'first vol found = ' edg@vol.1

The output on the console:

command = RMM SV OWNER(*)
num vols = 10
first vol found = V10001

When you use System REXX from the console, it makes a difference whether you are logged on to the console or not.

Logged on with a specific RACF® userid:
- System REXX creates an ACEE with this userid and for RMM subcommand authorization this ACEE and the appropriate DFSMSrmm related RACF profiles are used
- RMM uses this userid as the resource owner, if the OWNER operand is not specified in the issued command
- RMM records this userid as Last Change Userid
  Note: RMM can also record these special last change userids, which are not driven by a subcommand:
  *CAT
  
  Updates due to catalog status changes
  
  *HKP
  
  Updates due to inventory management
  
  *MIM
  
  Updates due to SARS MIM message interception
  
  *OAM
  
  Updates due to system-managed tape support
  
  *OCE
  
  Updates due to Open/Close/EOV support
  
  *UT
  
  Updates due to execution of EDGUTIL
  
  *WTO
  
  Updates due to message interception
- If your SEARCH subcommand results in CLIST processing; without RMMCLIST DD pre-allocated - RMM uses the user prefix (which is initially set to the RACF userid by System REXX) as HLQ for the dynamically allocated CLIST data set with RMMCLIST DD pre-allocated - the specified data set is used. Remember that when you dynamically allocate RMMCLIST DD within system REXX using the ALLOCATE command that the TSO convention for quoted and unquoted data set names applies and if an unquoted data set name is specified the user prefix is used as the HLQ for the data set
If not logged on :
- IEESYSAS (the jobname of a common System Address Space procedure) is used as the DFSMSrmm resource owner, Last Change userid and CLIST data set HLQ, instead of the RACF userid, that is used in the logged-on case.
- RMM subcommand authorization has no ACEE on which to base authorization checking, therefore most commands will fail authorization checking. The exceptions are those where the STGADMIN.EDG profiles specify a universal access, which enables users undefined to RACF to use RMM subcommands.
- If you attempt to pre-allocate a CLIST data set for the RMMCLIST DD using an unquoted data set name remember that there is no user prefix available, so the results will be as if you specified a quoted data set name. For example, "ALLOCATE DA(SYSREXX.CLIST)...." will result in CLIST data set 'SYSREXX.CLIST'; no prefix is added.