Usage Notes

  1. The CMS library DMSRTPRC must not be in storage when DMSTOEAG is invoked. You must purge the segment and drop the nucleus extension, as appropriate.
  2. The Rexx/370 Library EAGRTPRC must be in storage and the corresponding EAG message repository set when DMSTOEAG is invoked.

    The saved segment that contains EAGRTPRC can be loaded. Or, you can run the EAGRTPRC module to load the library and set the message repository; however, the module will return a non-zero return code. (The EAGRTPRC module is usually invoked by CMS when the first compiled exec is executed and assumes there is an exec to run. Invoking EAGRTPRC directly fails to provide it with an exec to run and the library initialization routine then assumes it was called by an internal routine that requested the address of a certain data field be returned in register 15. The result is a non-zero return code the value of which will vary depending on where the library is loaded in storage.)

  3. DMSTOEAG will check that the loaded EAGRTPRC library is at Release 3 or later and that it is not the REXX/370 Alternate Library.

    If the REXX/370 Library product, Release 3 or later, is not available or if only the REXX/370 Alternate Library is available, DMSTOEAG should not be used.

  4. DMSTOEAG issues the following return codes:
    0
    Operation successful; DMSRTPRC is now an alias for EAGRTPRC and EAGRTPRC is a Release 3 or later REXX/370 Library.
    1
    DMSRTPRC was located in storage (NucExt Query).
    2
    EAGRTPRC could not be located in storage (NucExt Query).
    3
    The loaded EAGRTPRC is the REXX/370 Alternate Library.
    4
    The loaded EAGRTPRC is not a REXX/370 Library.
    5
    The loaded EAGRTPRC is not at Release 3 or later.
    6
    The set EAG message repository could not be found (LangFind).
    25
    Insufficient storage to create an alias (NucExt Set).