Address space fails to initialize
If CTGRRMS is not running on the IBM® z/OS® image and ctgasi is used to call it, CTGRRMS might fail to start.
Symptom
The following messages are issued:
CTG6201I ctgasi - CTGRRMS Services Address Space Initiator.
CTG6200I ctgasi - CTG6200I (C) Copyright IBM Corporation 2005. All rights reserved.
CTG6237I ctgasi - starting up services address space.
CTG6216E ctgasi - ASCRE failed for CTGINIT, Post value = FFFFFFFF.
CTG6255E ctgasi - timed out waiting for address space to initialize.
CTG6240E ctgasi - the version of CTGINIT may be incompatible with ctgasi.
Probable cause
- CTGRRMS service is not starting because CTGINIT on the LNKLST is at the wrong version. CTGRRMS is trying to reuse an LX value that is corrupt. You can further diagnose this by checking the MVS™ System Log for an 052 abend from the CTGRRMS process. If this dump is taking place, probably with a reason code of 0512, (in R15 for the dump), the reserved LX value might be corrupt.
- The timeout and post value of FFFFFF might indicate that the version of SCTGLINK referred to in the LNKLST is for a CICS® Transaction Gateway V6.1, V7.0 or V7.1 and a ctgasi is for a V7.2 or later of the CICS Transaction Gateway. CTGRRMS is trying to reuse an LX value previously used for the CTGRRMS services and the LX value is in use by another process. This might be due to a previous CTGRRMS process not terminating completely, or completing but not releasing the LX value.
- CTGRRMS service is not starting because CTGINIT on the LNKLST is at the wrong version.
- CTGRRMS is trying to reuse an LX value that is corrupt. You can further diagnose this by checking the MVS System Log for an 052 abend from the CTGRRMS process. If this dump is taking place, probably with a reason code of 0512, (in R15 for the dump), the reserved LX value might be corrupt.
Action
- Change the LNKLST to refer to a SCTGLINK PDS from the same version of the Gateway as the ctgasi tool. When multiple releases of CICS Transaction Gateway are installed on the same LPAR, SCTGLINK and ctgasi from the latest installed version must be used.
- First check there is no CTGRRMS process running. If there is, force the process to end and
retry. If the problem persists you can renew the LX value by starting CTGRRMS
again using the force option: ctgasi -f.
This removes the old LX value and a new value is chosen. Because a limited number of LX values available on a IBM z/OS image, do not use this option unless there is no alternative. When all the LX values have been used you must IPL the IBM z/OS image before new services, including CTGRRMS services, can be started.