EQQV000 - EQQV045

EQQV000E

DUPLICATE NAMES IN THE ROUTOPTS SNA DESTINATIONS

One or names in the SNA keyword destination list in the ROUTOPTS inititialization statement is a duplicate of an existing name. These names are the application names of potential session partners and must be unique.

The NCF processing is terminated.

Correct the name (or names) in error and restart the subsystem.

EQQV001I

NCF APPLICATION STARTED

The NCF task has received control from the HCL Workload Automation for Z subsystem and is about to start initialization processing.

The NCF continues processing.

None.

EQQV002E

NCF APPLICATION TERMINATED - SETLOGON EXECUTION FAILURE

A VTAM SETLOGON macro used for enabling the NCF logon processing has failed. The reason for this failure is defined in detail by message EQQV015E, which precedes this message in the HCL Workload Automation for Z message log.

The NCF processing is terminated.

Correct the error (or errors) and restart the subsystem.

Review message EQQV015E to determine the exact reason for the failure.

EQQV003E

INITIALIZATION FAILED - SNA DESTINATION NOT SPECIFIED IN TRROPTS

In a tracker system, the NCF initialization processing failed because no partner application IDs were specified in the SNAHOST keyword of the TRROPTS statement

The NCF processing is terminated.

Add the missing information and restart the subsystem.

EQQV004E

NCF APPLICATION TERMINATED - PARAMETER PROCESSING FAILURE

The NCF initialization processing encountered an error in the parameters defined for it.

The NCF processing is terminated.

Correct all errors and restart the subsystem.

Review earlier messages in the HCL Workload Automation for Z message log to determine the exact reason for the failure.

EQQV005E

NCF APPLICATION TERMINATED - INITIALIZATION PROCESSING FAILURE

The NCF initialization processing failed. Messages issued preceding this message define the cause of the failure.

The NCF processing is terminated.

Correct all errors and restart the subsystem.

Review earlier messages in the HCL Workload Automation for Z message log to determine the exact reason for the failure.

EQQV006I

NCF APPLICATION ENDED

The NCF processing has completed and control is returned to the HCL Workload Automation for Z subsystem.

The NCF processing is terminated.

None.

EQQV007E

INITIALIZATION FAILED - SNA DESTINATION NOT SPECIFIED IN ROUTOPTS

In a controller system, the NCF initialization processing failed because no partner application IDs were specified in the SNA keyword of the ROUTOPTS statement.

The NCF processing is terminated.

Add the missing information and restart the subsystem.

EQQV008I

INITIALIZATION FAILED - SUBSYSTEM STOP REQUESTED

The NCF received a subsystem stop request while in the initialization phase. The NCF was most likely waiting for some other HCL Workload Automation for Z resource to become active.

The NCF processing is terminated.

None.

EQQV009E

INITIALIZATION FAILED - NCFAPPL KEYWORD NOT SPECIFIED OR INVALID

The NCF initialization processing failed because the NCFAPPL keyword was not specified or was invalid.

The NCF initialization processing is terminated.

Add the missing information and restart the subsystem.

EQQV010E

NIB BUILD PROCESSING FAILED - R15 = R15R00 = R00

The GENCB macro request issued to generate a NIB block did not complete normally.

The NCF processing is terminated.

If insufficient main storage was the cause of the failure, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the failure, search the IBM Support database for a solution at Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQV011E

RPL BUILD PROCESSING FAILED - R15 = R15R00 = R00

The GENCB macro request issued to generate an RPL block did not complete normally.

The NCF processing is terminated.

If insufficient main storage was the cause of the failure, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the failure, search the IBM Support database for a solution at Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQV012E

NIB EXLST BUILD PROCESSING FAILED - R15 = R15R00 = R00

The GENCB macro request issued to generate a NIB EXLST block did not complete.

The NCF processing is terminated.

If insufficient main storage was the cause of the failure, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the failure, search the IBM Support database for a solution at Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQV013E

ACB EXLST BUILD PROCESSING FAILED - R15 = R15R00 = R00

The GENCB macro request issued to generate a ACB EXLST block did not complete normally.

The NCF processing is terminated.

If insufficient main storage was the cause of the failure, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the failure, search the IBM Support database for a solution at Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQV014E

ACB BUILD PROCESSING FAILED - R15 = R15R00 = R00

The GENCB macro request issued to generate the NCF ACB did not complete normally.

The NCF processing is terminated.

If insufficient main storage was the cause of the failure, increase the region size and restart the HCL Workload Automation for Z subsystem. For any other cause of the failure, search the IBM Support database for a solution at Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQV015E

VTAM MACRO REQUEST FAILURE - DIAGNOSTIC INFORMATION: NODE = NODE, REQUEST = X'REQ' (NAMEREQ), RTNCD = X'RC' (DECRC) FDBK2 = X'FDBK2' (DFDBK2), SSENSMI = SMI USENSEI = USEI, SSENSEI = SSEI R00 = X'R00', R15 = X'R15'

An error occurred when a VTAM request was executed or scheduled. The variable items in the message provide diagnostic information and have the following meanings:
NODE
NCF application LU-name
REQ
VTAM request code in hexadecimal
NAMEREQ
VTAM request name
RC
RTNCD feedback field value from RPL in hexadecimal
DECRC
RTNCD feedback field value from RPL in decimal
FDBK2
FDBK2 feedback field value from RPL in hexadecimal
DFDBK2
FDBK2 feedback field value from RPL in decimal
SMI
System sense modifier information from RPL
USEI
User sense information from RPL
SSEI
System sense information from RPL
R00
Register 0 return code after a VTAM macro request
R15
Register 15 return code after a VTAM macro request.

The action taken depends on the severity of the error situation. The NCF attempts to continue processing, if at all possible. For the most serious errors, for example, undefined feedback code, the NCF abends with a dump and a user code.

Analyze the diagnostic information and the dump, if produced, to determine the cause of the failure. If this was not a user error, search the IBM Support database for a solution at Support.

Use the diagnostic information in the message to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQV016E

NAMEREQ REQUEST FAILURE - LU/APPLICATION NODE NOT FOUND

The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE could not be found. The most likely reason for the failure is either an invalid specification of an LU-name in the SNAHOST keyword of the TRROPTS initialization statement or the name NODE has not been properly defined to VTAM.

The NCF processing is terminated.

Review the name specified in the SNAHOST keyword. Make sure that it is correct and that a counterpart exists in the VTAM definition statements. Correct the items in error and restart NCF.

EQQV017E

NAMEREQ REQUEST FAILURE - LU/APPLICATION NODE NOT ACTIVE

The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE was not active.

The NCF processing is terminated.

Investigate why NODE suddenly became inactive. Restart NCF when NODE is active again.

EQQV018E

NAMEREQ REQUEST FAILURE - VTAM ERROR, OR NCP/VTAM INCOMPATIBILITY

The VTAM NAMEREQ request failed to complete successfully because there was an error in VTAM or an NCP/VTAM incompatibility. This message is preceded by message EQQV015E in the HCL Workload Automation for Z message log.

The NCF processing is terminated.

Restart NCF when the VTAM errors have been corrected.

Refer to message EQQV015E to determine the cause of the failure.

EQQV019E

SESSION SETUP FAILED - PLU=LU NOT AVAILABLE

The NCF has not been able to establish a session because of one of the following reasons:
  • The controller is not started.
  • The NCF task in the controller is not available.
  • The LU specified in the SNAHOST keyword of the TRROPTS initialization is not active or is not defined.
  • The controller has started without a valid current plan, for example at first startup after installation or after a REFRESH function (option 9.5).
The NCF retries every 10 seconds until it is successful, or until the subsystem is stopped, or until the NCF is deactivated.

The NCF continues to attempt to establish the LU-LU session.

Review the name specified in the SNAHOST keyword of the TRROPTS initialization statement and make sure that it is the correct one. If it is correct, ask the system operator at the controller system to activate or define the required resource.

EQQV020I

ACB SUCCESSFULLY CLOSED

The NCF has been successfully disconnected from VTAM.

The NCF termination processing continues.

EQQV021W

UNABLE TO CLOSE ACB

The NCF is unable to successfully disconnect from VTAM.

The NCF termination processing continues even though the ACB could not be closed.

None.

It is most likely that a VTAM error has caused this error. Check the system log for VTAM error messages that can be related to this failure.

EQQV022E

LOGON ATTEMPTED BY UNDEFINED LU/APPLICATION LU- CLSDST ISSUED

A session establishment attempt was made by a remote NCF application unknown to this host HCL Workload Automation for Z subsystem. This message is issued only for a NCF application at a HCL Workload Automation for Z host.

The request for the session is turned down by issuing a CLSDST macro. Processing continues for the HCL Workload Automation for Z host NCF application.

Stop the NCF task for which erroneous specifications have been given. Correct the specifications on the ROUTOPTS statement and restart the NCF.

It is most likely that a name in the ROUTOPTS SNA keyword list of names has been misspelled or left out entirely.

EQQV023E

LOGON REQUEST FOR LU/APPLICATION LU THAT IS ACTIVE - CLSDST ISSUED

A session establishment attempt is made from a remote NCF application that is already in session with the HCL Workload Automation for Z host NCF application. This message is issued only for a NCF application at a HCL Workload Automation for Z host.

The request for a session is turned down and NCF processing continues.

Stop all NCF tasks that have incorrect NCFAPPL keyword specifications. Correct the NCFAPPL specifications and restart the NCF tasks.

The most likely reason for this error is that more than one remote NCF application has the same LU-name specified. Check the NCFAPPL keyword of the OPCOPTS statement for all remote NCF applications and make sure that they are unique.

EQQV024I

ACB SUCCESSFULLY OPENED

The NCF has successfully established contact with VTAM and is ready for further VTAM processing.

The NCF processing continues.

None.

EQQV025I

ACB OPEN FAILURE (RC=X'RC') - VTAM SHUTTING DOWN

The NCF was unable to establish contact with VTAM due to an OPEN ACB failure. RC is the ACB error flag value in hexadecimal.

The NCF continues processing.

None.

EQQV026E

ACB OPEN FAILURE (RC=X'RC') - NCF IMPROPERLY DEFINED

The NCF was unable to establish contact with VTAM due to an OPEN ACB failure. RC is the ACB error flag value in hexadecimal.

The NCF processing is terminated.

Correct the problem and restart HCL Workload Automation for Z.

Use the return code to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQV027E

ACB OPEN FAILURE (RC=X'RC') - ABEND 1104 DUE TO SERIOUS ERROR

The NCF was unable to establish contact with VTAM due to an OPEN ACB failure. RC is the ACB error flag value in hexadecimal.

The NCF processing is abnormally terminated with a dump (abend code 1104).

Analyze the 1104 abend dump. If this was not a user error, contact IBM Software Support.

Use the R15 and R00 return codes to determine the cause of the error. For more information, refer to the appropriate documentation for the VTAM product installed on this z/OS system.

EQQV028W

ACB OPEN FAILED FOR THE LAST 2 MINUTES - VTAM NOT ACTIVE

The NCF failed to establish contact with VTAM during the last two minutes because VTAM was not active. The NCF attempts to establish contact every 10 seconds until contact is made. This message is issued every two minutes until contact is made.

THe NCF continues to attempt to establish contact with VTAM until contact is made or until the HCL Workload Automation for Z subsystem is stopped.

Ask your network operator to activate VTAM.

EQQV029I

VTAM TERMINATION, OR NCF DEACTIVATION, STOPPED SESSION SETUP ATTEMPTS

Session initiation attempts were stopped because VTAM is terminating or the NCF application was deactivated.

The NCF termination processing continues.

None.

EQQV031I

SUBSYSTEM STOP REQUEST TERMINATED SESSION SETUP ATTEMPTS

A remote NCF application was in the process of initiating a session when the subsystem was stopped.

The NCF termination processing continues.

None.

EQQV032I

SUBSYSTEM STOP REQUEST TERMINATED ACB OPEN ATTEMPTS

The NCF was in the process of establishing contact with VTAM when the subsystem was stopped.

The NCF termination processing continues.

None.

EQQV033E

ACB OPEN FAILED FOR THE LAST 2 MINUTES - NCF APPLICATION NOT ACTIVE

The NCF failed to establish contact with VTAM during the last two minutes because the NCF application was not activated. The NCF attempts to establish contact every 10 seconds until contact is made. This message is issued every two minutes until contact is established.

The NCF continues to attempt to establish contact with VTAM until contact is made or until the HCL Workload Automation for Z subsystem is stopped.

Ask the network operator to activate the VTAM LUs.

EQQV034E

NAMEREQ REQUEST FAILURE - LU/APPLICATION NODE INHIBITED

The VTAM NAMEREQ request failed to complete successfully because the LU-name NODE was inhibited. The most likely reason for the failure is that either the cross-domain NCF partner NODE has been deactivated or the partner VTAM system has been taken down.

If NAMEREQ is the REQSESS request, the NCF continues processing with session establishment attempts every 10 seconds. For other VTAM requests, NCF processing is terminated.

Ask the network operator to activate the VTAM or NCF application, or both applications, on the cross-domain partner system.

EQQV036I

SESSION HOME-DEST ESTABLISHED

A session has been established between the home application HOME and the destination application DEST.

The NCF continues processing.

None.

EQQV037I

SESSION HOME-DEST ENDED

The session between the home application HOME and the destination application DEST has ended.

The NCF continues processing.

None.

EQQV040I

CURRENTLY RUNNING WITH 'LU' AS CONTROLLER

The NCF in a HCL Workload Automation for Z tracker system has received a controller identification.

NCF continues processing.

None.

EQQV041E

THE NCF TASK IGNORED THE FOLLOWING ELEMENT ON THE NCF QUEUE DQE

An invalid element has been found by the NCF task. Possibly, the first four bytes of the element do not match the HCL Workload Automation for Z character string 'DQE '. (The fourth byte is a blank space.)

If EQQV039E was issued previously, EQQV041E is issued for all elements containing the destination specified in EQQV039E.

The NCF task does no more processing of the element, but continues normal processing.

If EQQV039E was issued previously, perform the actions described for that message. Otherwise, save the HCL Workload Automation for Z message log data set containing this error message. To collect appropriate documentation for problem determination, see the Diagnosis Guide and Reference manual, Chapter 3. Problem analysis procedures. Search the IBM Support database for a solution at Support.

EQQV042E

THE NCF TASK IGNORED THE FOLLOWING DATA, RECEIVED FROM 'NODE' DQE

The receiving NCF task did not recognize the type of data received from the application. This message is issued once for every invalid receive operation.

The NCF continues processing

Verify that the session parameters specified in the VTAM LOGMODE table are valid. Especially check that the ru-sizes are not zero.

If this message occurs during normal execution and the VTAM LOGMODE definitions are correctly specified, search the IBM Support database for a solution at Support.

EQQV043E

INVALID RU-SIZE SPECIFIED IN 'LU' SESSION PARAMETERS

The ru-sizes specified in the session parameters are not valid.

The NCF continues processing, but the specified session is not established.

Verify that the ru-sizes specified in the tracker node are valid. If necessary, specify different ru-sizes, and stop and restart the tracker NCF.

EQQV044E

OPNDST FAILURE WHEN CONFIRMING SESSION WITH TRACKER 'LU'

The OPNDST macro issued to confirm session establishment between the NCF controller and a remote tracker failed. The most likely reason for the failure is that either there is no active route back to the tracker from the controller node or the VTAM environment of the tracker requesting the session is going down.

The NCF continues processing and the NCF controller logon exit is ready to handle subsequent logon attempts from the remote tracker.

Ask the network operator to activate the necessary links to secure an active route back to the tracker.

EQQV045E

THE NCF TASK HAS BEEN CONTACTED BY AN UNKNOWN DESTINATION: LU

The NCF task has recognized a session control request from a destination that is not defined in the ROUTOPTS or TRROPTS initialization statement. One possible reason for this message is that an APPC program is attempting to allocate a conversation with another APPC program, but is mistakenly using the LU name of the NCF program.

A bind request from an unknown destination is rejected and the NCF continues normal processing. If an APPC program is attempting to allocate a conversation it gets a failing return code from the APPC service routine.

If the NCF task should support the destination specified in this message, update the ROUTOPTS or TRROPTS initialization statement and restart the HCL Workload Automation for Z subsystem. If an APPC program is attempting to allocate a conversation with APPC functions in a HCL Workload Automation for Z controller system, inform the owner of the APPC program at the remote location of the LU name that is to be used if APPC services are to be provided. This LU name is defined by an APPCPMxx member in the SYS1.PARMLIB library.

Use the name of the unknown destination to determine which program and which location is attempting to access NCF resources.