D.4 ASC Messages

Messages beginning with ASC are issued by ASCLIENT, the z/OS Platform Services Process.

ASC0000I command response.

Explanation: This message is issued in response to a DISPLAY command.

ASC0001I productVersion was started on date at time.

Explanation: This message is issued during ASCLIENT startup.

ASC0004I n request(s) found on existing queue.

Explanation: ASCLIENT found n requests awaiting processing on the in-storage queue during a warm startup.

ASC0005E Unable to load interface module moduleName: abend abendCode.

Explanation: ASCLIENT attempted to load moduleName into ECSA, but the load macro failed. Register 1 contains system completion code abendCode.
Action: Respond as appropriate for abendCode.

ASC0007I productVersion has ended.

Explanation: ASCLIENT has shut down in response to a STOP command.

ASC0010I statistics line.

Explanation: This message is used to write statistical information to the console.

ASC0011I Command entered was: command_text.

Explanation: ASCLIENT accepted a MODIFY command as valid, and attempts to execute it.

ASC0012I New parameter file applied.

Explanation: ASCLIENT has updated its configuration in response to a CONFIG xx command.

ASC0013I Log switched.

Explanation: The LOGSWITCH command was entered. The ASCLOG file has been closed, freed, reallocated, and reopened. The previous log is available for processing.

ASC0020E WARM and COLD parameters are mutually exclusive.

Explanation: The startup parameters WARM and COLD were both found in the PARM string in the ASCLIENT startup procedure.
Action: Remove one of the two parameters from the PARM string.

ASC0021E Module moduleName does not contain valid global token. Module not loaded.

Explanation: During configuration file processing, ASCMAIN was unable to set an internal token value as part of loading module ASCUSER. If this occurs during startup, ASCMAIN terminates with a return code of 8. If the message appears after a CONFIG command, the new configuration is not accepted.
Action: The copy of ASCUSER or ASCMAIN in the ASCLIENT STEPLIB could be corrupted. Reload the load library from the distribution media and compare these modules with the copies in the ASCLIENT STEPLIB. If you cannot account for any differences, re-create the load library from the distribution, and reinstall any patches you have applied.

ASC0022E Invalid keyword beginning with: text.

Explanation: An invalid keyword appears in the PARM string for ASCLIENT. ASCLIENT terminates.
Action: Correct the PARM string and restart ASCLIENT.

ASC0023E Invalid parameter beginning with: text.

Explanation: A valid command in the PARM string is followed by an invalid operand. ASCLIENT terminates.
Action: Correct the PARM string and restart ASCLIENT.

ASC0024E Name/Token Services function error: description.

Explanation: z/OS Name/Token Services returned the unexpected error described in the message.
Action: Make note of the message text, collect diagnostic information, and contact Support.

ASC0025E Parameter file error, line n: description.

Explanation: The syntax error described in the message was detected in the configuration file at line n. If this occurs at startup, ASCLIENT terminates. If this occurs as a result of a CONFIG command, the new configuration is not loaded, and ASCLIENT continues with its current configuration.
Action: Correct the syntax error in the configuration file, and either restart ASCLIENT, or reissue the CONFIG command.

ASC0026E Unable to process parameter file name.

Explanation: The ASCPARMS data set name could not be determined. The most likely cause is that ASCPARMS is not defined in the ASCLIENT JCL.
Action: Ensure that ddname ASCPARMS is defined and specifies a valid configuration file data set.

ASC0027E Unable to free ASCPARMS: dynalloc error code is error, info.

Explanation: ASCMAIN encountered an error while trying to deallocate the configuration file during configuration file processing. The dynamic allocation error and information codes appear in the message.

Dynamic allocation return codes and reason codes are documented in the IBM publication z/OS Programming: Authorized Assembler Services Guide.

Action: Respond as appropriate for the dynamic allocation error and information codes.

ASC0028E No parametertype statements in parameter file.

Explanation: ASCLIENT did not find any parametertype statements in the configuration file. The parameter type named in the message is a required parameter. Configuration file syntax checking continues. If this error occurs during startup, ASCLIENT terminates. If the error occurs as the result of a CONFIG command, the ASCLIENT configuration is not changed.
Action: If the missing statement type is AUTHENTICATION, add appropriate AUTHENTICATION statements to the parameter file. If the missing statement type is KEY, add one KEY statement to the parameter file. The key value must match the DES encryption key specified in the Core Driver configuration object for the platform. Then, either restart ASCLIENT (for failures during startup) or reissue the CONFIG command (for configuration changes during execution).

ASC0029E Unable to load name-token module modulename.

Explanation: One or more of the z/OS callable services routines (IEANTCR, IEANTRT, or IEANTDL) could not be located in LPA or the linklist.
Action: These routines are shipped with z/OS in CSSLIB. Check your SMP target zone for z/OS to see where these load modules reside. If SYS1.CSSLIB contains these modules but is not in your linklist, consider adding it. The caller-side interface module ASCUSER also requires IEANTRT and is not able to call ASCLIENT without it.

ASC0032E Unable to load ASCHOST.

Explanation: During initialization, ASCLIENT did not find module ASCHOST in STEPLIB. ASCLIENT terminates.
Action: Ensure that load module ASCHOST is available in the ASCLIENT STEPLIB concatenation.

ASC0033E Internal error occurred: description.

Explanation: An unexpected error occurred during normal processing. The error description provides additional information. If this message is issued by an ASCLIENT subtask, the subtask issues a User 0001 ABEND with a dump. If the message is issued by the ASCLIENT main task, ASCLIENT terminates.
Action: Make note of the message text, collect diagnostic information, and contact Support.

ASC0036E DELAY.PREFGRP value of pg_delay is less than DELAY.AUTHENTICATION value of ag_delay.

Explanation: The DELAY.PREFGRP and/or DELAY.AUTHENTICATION statements were found in the ASCLIENT configuration file. The value for DELAY.PREFGRP (either the value specified or the default of 5) is less than the value specified or defaulted to for DELAY.AUTHENTICATION. The value of DELAY.PREFGRP must equal or exceed that of DELAY.AUTHENTICATION.
Action: Correct the DELAY statement(s) in the ASCLIENT configuration file, then reload the configuration file or restart ASCLIENT.

ASC0037E Log not switched; ASCLOG was allocated by DD statement.

Explanation: The LOGSWITCH command was entered, but ASCLIENT can cause a log switch only if the ASCLOG DD statement is dynamically allocated (not specified in the ASCLIENT JCL).
Action: If you need to use the LOGSWITCH command, remove the ASCLOG DD statement from the ASCLIENT JCL and restart ASCLIENT.

ASC0050E Invalid command beginning with: text.

Explanation: An invalid command was entered as an ASCLIENT MODIFY command.
Action: Correct and reissue the command.

ASC0051E Invalid operand beginning with: text.

Explanation: A valid ASCLIENT MODIFY command was entered, but one of its operands was not recognized.
Action: Correct and reissue the command.

ASC0052E STOP/MODIFY command processing error: description.

Explanation: An internal QEDIT error occurred during ASCLIENT STOP/MODIFY processing.
Action: Make note of the message text, collect diagnostic information, and contact Support.

ASC0070E Name-token services error in exitname.

Explanation: The security system exit encountered an unexpected error while trying to find the environment.
Action: Make note of the message text, collect diagnostic information, and contact Support.

ASC0071I Userid user will be authenticated locally.

Explanation: No Core Drivers could be contacted to authenticate a user.
Possible Cause: The ASCLIENT started task is not running.

TCP/IP is not available.

No Core Drivers responded to a request.

Action: Review the started task log files for more information.

ASC0073I ACF2 password not changed. Use the LOGON command to change your password.

Explanation: The user attempted to change the password using the ACF command. This is disallowed. Change the password using the LOGON command, using the Novell Client, or from another system that is running Platform Services.
Action: None; informational only. This message is a ROUTCDE=11 WTO and appears on z/OS consoles that are set to display ROUTCDE=11 messages.

ASC0074I ACF2 password not changed. Unknown error in ACF2 new-password exit.

Explanation: ASCLIENT returned an unexpected response to ASCNPXIT during a password change request. The user's password is not changed in the security database. Whether or not the password is changed in eDirectory depends on the nature of the error.
Action: Examine the ASCLIENT task logs to see what messages or errors were returned to ASCLIENT from the Core Driver. Contact Support if you cannot determine the cause of the error.