ADAK* System Messages

This message, written to the console, indicates the destination for ADAK* installation messages, issued by the Adabas CICS installation program ‘xxxxxxxx’, when configured to use a CICS transient data queue ‘qname’ using the IMSGDEST and IMQNAME parameters of the MACIOPT macro, as follows:

MACIOPT ENTRY=GLOBAL,IMSGDEST=TDQ,IMQNAME=qname

If the specified transient data queue is available, the ADAK001 message is issued indicating its use.

If the specified transient data queue is not available, the message destination will revert to the console and the ADAK001 message issued to reflect this.

The ADAK001 message is not issued when IMSGDEST=CONSOLE (the default) or IMSGDEST=BOTH.

No action is required for this informational message.

This message indicates the start of the Adabas CICS installation program ‘xxxxxxxx’ (default ADACIC0), the transaction ID ‘tttt’ under which it is executing, and its version ‘vrs’.

No action is required for this informational message.

This message indicates whether the ACIOPT load module (created using the MACIOPT macro) is linked to the Adabas CICS installation program identified in the previous ADAK002 message, or if the installation program had to dynamically load it. In addition, this message displays:

• The number ‘nnn’ of CICS environments to establish – derived from the number of Globals table entries defined using the GTNAME parameter of the MACIOPT macro.

• The destination of installation messages issued by the installation program - defined using the IMSGDEST and IMQNAME parameters of the MACIOPT macro.

No action is required for this informational message.

This message displays some basic information regarding the CICS system for the current job ‘jobname’.

Refer to the CICS INQUIRE SYSTEM documentation for more information on these options.

No action is required for this informational message.

This message indicates the start of processing for the globals table ‘gblname’ as defined using the GTNAME parameter of the MACIOPT macro.

No action is required for this informational message.

This message indicates that the globals table, previously identified by the ADAK010 message, has been successfully loaded at address ‘hhhhhhhh’.

No action is required for this informational message.

This message identifies the name of the Application stub ‘stubname’ specified by the ENTPT parameter of the LGBLSET macro within the globals table previously identified by the ADAK010 message.

No action is required for this informational message.

This message identifies the name of the Adabas TRUE ‘truename’ specified by the TRUENM parameter of the LGBLSET macro within the globals table previously identified by the ADAK010 message.

No action is required for this informational message.

This message indicates the Adabas TRUE, previously identified by the ADAK016 message, is being installed.

No action is required for this informational message.

This message indicates that the Global Work Area for the Adabas TRUE, previously identified by the ADAK016 message, has been successfully established at address ‘hhhhhhhh’.

No action is required for this informational message.

This message indicates that the Application stub module, previously identified by the ADAK014 message, has been successfully loaded at address ‘hhhhhhhh’.

No action is required for this informational message.

This message indicates the Adabas TRUE, previously identified by the ADAK016 message, is being started.

No action is required for this informational message.

This message indicates the Application stub, previously identified by the ADAK014 message, is being initialized.

No action is required for this informational message.

This message indicates the version ‘vrs’ of the Application stub previously identified by the ADAK014 message and the version ‘nn’ of the MACINS macro used to create the ACINAMES module linked to this application stub. The globals table ‘gblname’ and the Adabas TRUE ‘truename’ are those that are defined using the GTNAME and TRUENAME parameters of the MACINS macro.

This is an informational message but in the event of problems ensure the ‘gblname’ and ‘truename’ specified in this message are the same as in the previous ADAK010 and ADAK016 messages respectively.

This message indicates the address ‘hhhhhhhh’ of the Application stub’s direct call interface.

No action is required for this informational message.

This message indicates communication with the Adabas SVC number ‘nnn’ is being established. The SVC number is defined in the globals table, previously identified by the ADAK010 message, using the SVCNO parameter of the LGBLSET macro.

No action is required for this informational message.

This message indicates the address ‘hhhhhhhh’ of the ID table corresponding to the Adabas SVC number previously identified by the ADAK032 message.

No action is required for this informational message.

This message indicates the initializing of the COR-based Add-ons (for example, Adabas Fastpath, Adabas Vista, and Adabas Transaction Manager) and only occurs if the COR=YES parameter option of the LGBLSET macro is defined in the globals table previously identified by the ADAK010 message. See also message ADAK054.

No action is required for this informational message.

This message indicates the default database ID defined in the globals table, previously identified by the ADAK010 message, using the LOGID parameter of the LGBLSET macro.

No action is required for this informational message.

This message indicates that a UB type of TASK is defined in the globals table, previously identified by the ADAK010 message, using the UBTYPE parameter of the LGBLSET macro.

No action is required for this informational message.

This message indicates that a UB type of POOL with ‘nnnnn’ UB entries is defined in the globals table, previously identified by the ADAK010 message, using the UBTYPE and NUBS parameters of the LGBLSET macro. The UB pool has been successfully allocated at address ‘hhhhhhhh’.

No action is required for this informational message.

This message indicates whether the use of a user exit 1 is defined in the globals table, previously identified by the ADAK010 message, using the USERX1 and LX1NAME parameters of the LGBLSET macro. If the user exit is linked to the globals table, its address is displayed by ‘hhhhhhhh’.

No action is required for this informational message.

This message indicates whether the use of a user exit 2 is defined in the globals table, previously identified by the ADAK010 message, using the USERX2 and LX2NAME parameters of the LGBLSET macro. If the user exit is linked to the globals table, its address is displayed by ‘hhhhhhhh’.

No action is required for this informational message.

This message indicates the values for the specified parameters defined in the globals table previously identified by the ADAK010 message.

No action is required for this informational message.

This message indicates the address ‘hhhhhhhh’ of any REVIEW exit1 and/or exit2 linked to the globals table previously identified by the ADAK010 message. If present, the version ‘vrs’ of the exit is displayed.

If AUDIT=YES (see previous ADAK048 message), the addresses and version will be displayed as ‘n/a’.

No action is required for this informational message.

This message indicates the address ‘hhhhhhhh’ of any AUDIT exit1 and/or exit2 linked to the globals table previously identified by the ADAK010 message. If present, the version ‘vrs’ of the exit is displayed.

If AUDIT=NO (see previous ADAK048 message), the addresses and version will be displayed as ‘n/a’.

No action is required for this informational message.

This message indicates whether the use of the System Coordinator (COR) is defined in the globals table previously identified by the ADAK010 message. If the COR stub CORS03 is linked to the globals table, its address is displayed by ‘hhhhhhhh’ and its version by ‘vrs’.

No action is required for this informational message.

This message indicates whether the use of a DBID/SVC routing table is defined in the globals table, previously identified by the ADAK010 message, using the DYNDBSVC and DBSVCTN parameters of the LGBLSET macro. If the routing table is linked to the globals table, its address is displayed by ‘hhhhhhhh’.

No action is required for this informational message.

This message indicates whether the use of the Adabas security interface is defined in the globals table previously identified by the ADAK010 message.

No action is required for this informational message.

This message indicates whether the use of the Resource manager interface is defined in the globals table previously identified by the ADAK010 message.

No action is required for this informational message.

This message indicates whether the use of the Adabas VSAM Bridge is defined in the globals table previously identified by the ADAK010 message.

No action is required for this informational message.

This message is only applicable when the globals table previously identified by the ADAK010 message is defined with RMI=YES and COR=YES, and the Adabas Transaction Manager is installed. The resynchronization process automatically performed by the Adabas CICS installation process has recognized that the Adabas Transaction Manager is not currently active.

No action is required for this informational message since resynchronization will automatically occur when the Adabas Transaction Manager is restarted. However, we strongly recommend that the Adabas Transaction Manager is active when CICS systems are started.

This message is only applicable when the globals table previously identified by the ADAK010 message is defined with RMI=YES and COR=YES, and the Adabas Transaction Manager is installed and active. The resynchronization process automatically performed by the Adabas CICS installation process has been initiated.

No action is required for this informational message.

This message indicates the end of processing for the globals table ‘gblname’.

No action is required for this informational message.

This message indicates the end of processing for the Adabas CICS installation program ‘xxxxxxxx’. The number of successfully installed CICS environments ‘xxx’ and the number of installations attempted ‘yyy’ is displayed.

No action is required for this informational message but if ‘xxx’ is not equal to ‘yyy’ then refer to previous ADAK* messages for an indication of why an installation may have failed.

This is a generic message issued whenever the execution of a CICS API function fails. The values displayed are those returned to the Adabas CICS Installation program at the time of failure. This ADAK081 message will be immediately preceded by another ADAK* message indicating the failed CICS API function.

Refer to the ADAK* message preceding the ADAK081 message and, if necessary, refer to CICS documentation for an explanation of the values in the ADAK081 message to determine the reason for the failure.

This message indicates a failure of EXEC CICS INQUIRE SYSTEM.

Refer to the error text in the message, and, if necessary, use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates a failure of EXEC CICS ASSIGN.

Refer to the error text in the message, and, if necessary, use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates a failure of EXEC CICS LOAD to dynamically load the installation options table ACIOPT.

Check the DFHRPL concatenated libraries to ensure that the ACIOPT module is available to the CICS region. If necessary, use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates that the ACIOPT module loaded is not recognizable.

Ensure there is only one ACIOPT module in the DFHRPL concatenation libraries and that it is created from the MACIOPT macro.

This message indicates a failure of EXEC CICS LOAD to dynamically load the globals table ‘xxxxxxxx’.

Check the DFHRPL concatenated libraries to ensure that the module ‘xxxxxxxx’ is available to the CICS region. If necessary, use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates a failure of EXEC CICS GETMAIN to allocate a UB-pool of length ‘hhhhhhhh’.

Refer to the error text in the message and ensure the number of UB entries defined in the globals table, previously identified by the ADAK010 message, using the NUBS parameter of the LGBLSET macro is correct. If necessary, use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates a failure of EXEC CICS EXTRACT EXIT to return the address of the Global Work Area associated with the Adabas TRUE previously identified by the ADAK016 message.

Use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates a failure of EXEC CICS LOAD to dynamically load the Application stub.

Refer to the error text in the message and check the DFHRPL concatenated libraries to ensure that the Application stub module previously identified by the ADAK014 message is available to the CICS region. If necessary, use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates a failure of EXEC CICS LOAD to dynamically load the DBID/SVC routing table ‘xxxxxxxx’ .

Check the DFHRPL concatenated libraries to ensure that the DBID/SVC routing table ‘xxxxxxxx’ is available to the CICS region. If necessary, use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine ethe reason for the failure.

This message indicates a failure of EXEC CICS ENABLE PROGRAM(truename) to ‘Install’ or ‘Start’ the Adabas TRUE previously identified by the ADAK016 message.

Refer to the error text in the message, and, if necessary, use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates a failure to initialize the Application stub previously identified by the ADAK014 message.

Refer to the error text, response code and sub-code in the message, and, if necessary, use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates a failure to establish the address of the Adabas ID table.

Check the Adabas SVC number in the globals table, previously identified by the ADAK010 message, which is defined using the SVCNO parameter of the LGBLSET macro.

This message indicates a failure to establish the address of the Application stub’s direct call interface.

Ensure the Application stub, previously identified by the ADAK014 message, is correct.

This message indicates a failure of EXEC CICS LINK to call the RESYNC program ATMRMIRS.

Use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates the call to the RESYNC program ATMRMIRS returned with an error.

Refer to the response code and return code in the message and, if necessary, contact Software AG support.

After an installation failure, this message indicates program ‘xxxxxxxx’ was successfully uninstalled.

No action is required for this informational message. Refer to previous ADAK* messages for the reason the installation failed.

After an installation failure, this message indicates that the attempt to EXEC CICS FREEMAIN the previously allocated UB-pool failed.

Refer to previous ADAK* messages for the reason the installation failed and use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.

This message indicates a failure of EXEC CICS INQUIRE TDQUEUE(xxxx) when checking for the availability of the specified queue name ‘xxxx’ when configured in the Adabas installation options table ACIOPT using the IMSGDEST and IMQNAME parameters of the MACIOPT macro.

Use the relevant CICS documentation to interpret the error values reported in the subsequent ADAK081 message to determine the reason for the failure.