0353E

REQUEST requestname IS A CLASSED REQUEST AND CANNOT BE RELEASED.

Reason:

You issued the RELEASE command for a request that was scheduled with the CLASS option. Requests scheduled with the CLASS option can only begin initiating after the VM:Schedule operator starts the class with the CLASS START command.

Action:

None.

0355E

THE STRING ENTERED IS AN INCORRECTLY QUOTED PASSWORD PHRASE

Reason:

An incorrect string was entered in response to a password prompt. You are prompted again to enter a password.

Action:

Enter the password again at the prompt. If you think that you entered your password correctly, contact your system administrator for further assistance.

0356E

THE PASSWORD ENTERED IS TOO LONG.

Reason:

You entered a string longer than 200 characters in response to a password prompt. The system prompts you again for the password.

Action:

Enter the password again at the prompt. If you think that you entered your password correctly, contact your system administrator for further assistance.

0357E

A TRADITIONAL PASSWORD CANNOT CONTAIN BLANKS.

Reason:

You responded to a password prompt with a string that resolved to 8 characters or less but that contained embedded blanks. The system prompts you again for the password.

Action:

Enter the password again at the prompt. If you are entering a traditional password, do not include blanks in the password response. If you think that you entered your password correctly, contact your system administrator for further assistance.

0359E

COULD NOT VALIDATE PASSWORD - DMSPASS RETURN CODE: code

Reason:

DMSPASS could not validate the password. This error is probably due to authorization issues with DIAG X'88'.

Action:

If the return code is 32 or 36, you must grant authorization for CA VM:Schedule to use DIAGNOSE X’88’ through your ESM. Also, OPTION DIAG88 must be enabled in the CA VM:Schedule service machine userid z/VM directory entry. Otherwise, verify the documentation for the IBM DMSPASS callable routine for the meaning of the return code or contact your system administrator.

0360E

INVALID RETURN CODE code FROM userexit-name USER EXIT.

Reason:

The user exit returned the code that is not a valid return code for the user exit. The command or activity that is associated with the user exit ends abnormally.

Action:

Correct the user exit to pass back only valid return codes, as documented for the user exit.

0361W

EXPECTED VALUE NOT STACKED BY userexit-name USER EXIT.

Reason:

VM:Schedule expected information to be on the program stack after a call to the indicated user exit, and no information is stacked. The command or activity causing the user exit call fails.

Action:

Correct the user exit logic to stack the appropriate information before returning to VM:Schedule processing.

0362E

vmschedule IS NOT FULLY INITIALIZED; COMMAND REJECTED.

Reason:

VM:Schedule is waiting for the confirmation of the date verification before it can allow most commands to continue.

Action:

Wait a minute and try again. If this message persists, alert your operations staff or system administrator that the date verification reply for VM:Schedule is outstanding.

0363E

INSTALLATION EXIT exit ALREADY SPECIFIED.

Reason:

The userexit already exists in the configuration file. Each userexit must only be specified once.

Action:

Delete out all but the required configuration file record for the userexit.

0364W

ERROR code FROM CALL TO userexit-name USEREXIT

Reason:

The indicated error occurred during a call to the user exit named in the message.

Action:

The user exit is ignored and the command continues normally. Contact the system administrator to investigate the user exit logic error.

0365I

QUERY COMMAND OUTPUT COMPLETE

Reason:

This message indicates the command is complete though no output may have been produced.

Action:

None. This is an informational message.

0366E

OPTION ‘option’ CANNOT BE USED OUTSIDE OF A SINGLE SYSTEM IMAGE ENVIRONMENT

Reason:

The indicated option is only valid when CA VM:Schedule is initialized in an IBM Single System Image Environment.

Action:

Do not specify the option unless CA VM:Schedule is operating in a Single System Image environment.

0367E

OPTION ‘option’ CANNOT BE USED WITH request-type REQUESTS

Reason:

The indicated option is not valid with the type of request specified in the message.

Action:

Change your request type or don’t use the option to correct this error.

0368E

SYSTEM NAME ‘system-name’ IS NOT A VALID MEMBER OF THIS SINGLE SYSTEM IMAGE CLUSTER

Reason:

You specified a SYSNAME option, but you did not enter a valid system name for the Single System Image cluster where CA VM:Schedule is running.

Action:

Enter a valid system name for the Single System Image cluster where CA VM:Schedule is running.

0369E

READER FILE nnn CONTAINS INVALID DATA. THE FILE IS HELD.

Reason:

CA VM:Schedule received a reader file it cannot process. These files usually are associated with job monitoring and tracking and can be sent from CA VM:Batch or from a userid executing a scheduled request.

Action:

The file is ignored. Processing continues. The bad file is left in the reader on hold. The job associated with the file should be cancelled and re-submitted with the appropriate scheduling options.

0370I

CA VM:Schedule is configured for Single System Image processing.

Reason:

This message confirms that you are running CA VM:Schedule in Single System Image mode.

Action:

None.

0371W

CA VM:Schedule is not running in a Single System Image environment, so the SSI configuration file record is ignored.

Reason:

The CA VM:Schedule configuration file, VMSCHED CONFIG, contains an Single System Image (SSI) configuration file record but the service machine is not running in an SSI environment. The SSI configuration file record is ignored.

Action:

None.

To enable Single System Image processing in the product, enable your SSI environment, then re-initialize CA VM:Schedule.