Developer for System z, Version 7.6.x

# Error messages that you can ignore

Some of the keywords associated with CICS® command have changed over the years, but have been retained for compatibility reasons. A few of these obsolete keywords are incorrectly flagged as invalid by the syntax checker. These are listed in Table 1, together with an explanation of the problem, and the action that you should take if you encounter it.

Table 1. Keywords incorrectly flagged as invalid by the syntax checker
Command | Description | Acrion
--- | --- | ---
ALLOCATE | The NOSUSPEND keyword is an alternative to the NOQUEUE keyword for this command. If you specify NOSUSPEND, the syntax checker returns: `Invalid command option 'NOSUSPEND'` | You can ignore this error because the syntax is correct.
ASSIGN | The OPSECURITY and OPERKEYS keywords are supported for compatibility reasons. If you specify either of these keywords, the syntax checker returns: `Invalid command option 'OPSECURITY'``Invalid command option 'OPERKEYS` | You can ignore these errors because the syntax is correct.
CSD GETNEXTRSRCE | If using a resource name (For example: PROGRAM) instead of the RESTYPE keyword the syntax checker will return: `Invalid command option 'PROGRAM'.` | You can ignore this error because the syntax is correct
DELETE | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
DELETEQ TS | The keyword TS is optional for this command. (This is for compatibility with earlier releases, and is not documented.) If you do not specify the TS option, the syntax checker assumes that the command is DELETEQ TD, and returns: `Command is ambiguous, 'TD' has been assumed` This causes other options to be flagged as invalid. | You can ignore this error because the syntax is correct. However, if you want to check the other options that were flagged as invalid you must specify TS to check that there are no other errors.
DEQ | A CVDA value of LUW is supported as an alternative to UOW for compatibility reasons. If you specify LUW, the syntax checker returns: `Invalid command option 'LUW` | You can ignore this error because the syntax is correct.
DOCUMENT RETRIEVE | The CLNTCODEPAGE keyword is an alternative to the CHARACTERSET keyword for this command. If you specify CLNTCODEPAGE, the syntax checker returns: `Invalid command option 'CLNTCODEPAGE'` | You can ignore this error because the syntax is correct.
ENDBR | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
ENQ | A CVDA value of LUW is supported as an alternative to UOW for compatibility reasons. If you specify LUW, the syntax checker returns: `Invalid command option 'LUW` | You can ignore this error because the syntax is correct.
INQUIRE DSNAME | The BKOUTSTATUS option is obsolete on this command, but has been retained for compatibility with earlier releases. If you specify BKOUTSTATUS, the syntax checker returns: `Invalid command option 'BKOUTSTATUS'` | You can ignore this error because the syntax is correct. However, CICS will accept the keyword and issue an informational message
INQUIRE JOURNALNUM | This command is obsolete and is retained only for compatibility reasons. If you specify this command, the syntax checker returns: `Invalid command option 'JOURNALNUM'` This might cause other options to be flagged as invalid. | You can ignore these errors because the syntax is correct. However, CICS will accept the command and issue an informational message
INQUIRE NETNAME | The SCREENWIDTH and SCREENHEIGHT keywords have been replaced by SCRNHT and SCRNWD on this command, but are supported for compatibility reasons. If you specify either of these keywords, the syntax checker returns: `Invalid command option 'SCREENWIDTH'``Invalid command option 'SCREENHEIGHT'` | You can ignore these errors because the syntax is correct.
INQUIRE PROGRAM | The JVMDEBUG option is obsolete on this command, but has been retained for compatibility with earlier releases. If you specify JVMDEBUG, the syntax checker returns: `Invalid command option 'JVMDEBUG'` | You can ignore this error because the syntax is correct. CICS returns NODEBUG as the CVDA value.
INQUIRE TASK | The DTB option is obsolete and was replaced by INDOUBT on this command. However, it has been retained for compatibility with earlier releases. If you specify DTB, the syntax checker returns: `Invalid command option 'DTB'` | You can ignore this error because the syntax is correct. CICS returns NOTSUPPORTED as the CVDA value.
INQUIRE TERMINAL | The SCREENWIDTH and SCREENHEIGHT keywords have been replaced by SCRNHT and SCRNWD on this command, but are supported for compatibility reasons. If you specify either of these keywords, the syntax checker returns: `Invalid command option 'SCREENWIDTH'``Invalid command option 'SCREENHEIGHT'` | You can ignore these errors because the syntax is correct.
INQUIRE VOLUME | This command is obsolete and is retained only for compatibility reasons. If you specify this command, the syntax checker returns: `Invalid command option 'VOLUME'` This might cause other options to be flagged as invalid. | You can ignore these errors because the syntax is correct. However, CICS will accept the command and issue an informational message
READ | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
READNEXT | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
READPREV | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
READQ TS | The keyword TS is optional for this command. (This is for compatibility with earlier releases, and is not documented.) If you do not specify the TS option, the syntax checker assumes that the command is READQ TD, and returns: `Command is ambiguous, 'TD' has been assumed` This causes other options to be flagged as invalid. | You can ignore this error because the syntax is correct. However, if you want to check the other options that were flagged as invalid you must specify TS to check that there are no other errors.
RESETBR | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
REWRITE | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
SET DSNAME | The FAILEDBKOUT, NORMALBKOUT and BKOUTSTATUS options are obsolete on this command, but have been retained for compatibility with earlier releases. If you specify any of these keywords, the syntax checker returns: `Invalid command option 'FAILEDBKOUT'``Invalid command option 'NORMALBKOUT'``Invalid command option 'BKOUTSTATUS'` | You can ignore these errors because the syntax is correct. However, CICS will accept the keywords and issue informational messages
SET JOURNALNUM | This command is obsolete and is retained only for compatibility reasons. If you specify this command, the syntax checker returns: `Invalid command option 'JOURNALNUM'` This might cause other options to be flagged as invalid. | You can ignore these errors because the syntax is correct. However, CICS will accept the command and issue an informational message
SET VOLUME | This command is obsolete and is retained only for compatibility reasons. If you specify this command, the syntax checker returns: `Invalid command option 'VOLUME'` This might cause other options to be flagged as invalid. | You can ignore these errors because the syntax is correct. However, CICS will accept the command and issue an informational message
STARTBR | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
UNLOCK | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
WEB READ | The CLNTCODEPAGE keyword is an alternative to the CHARACTERSET keyword for this command. If you specify CLNTCODEPAGE, the syntax checker returns: `Invalid command option 'CLNTCODEPAGE'` | You can ignore this error because the syntax is correct.
WEB RECEIVE | The CLNTCODEPAGE keyword is an alternative to the CHARACTERSET keyword for this command. If you specify CLNTCODEPAGE, the syntax checker returns: `Invalid command option 'CLNTCODEPAGE'` | You can ignore this error because the syntax is correct.
WEB SEND | The CLNTCODEPAGE keyword is an alternative to the CHARACTERSET keyword for this command. If you specify CLNTCODEPAGE, the syntax checker returns: `Invalid command option 'CLNTCODEPAGE'` | You can ignore this error because the syntax is correct.
WEB STARTBROWSE | The CLNTCODEPAGE keyword is an alternative to the CHARACTERSET keyword for this command. If you specify CLNTCODEPAGE, the syntax checker returns: `Invalid command option 'CLNTCODEPAGE'` | You can ignore this error because the syntax is correct.
WRITE | You can use the keyword DATASET as an alternative to FILE for this command. (This is for compatibility with earlier releases, and is not documented.) If you do this, the syntax checker returns: `Invalid command option 'DATASET'` This might cause other options to be flagged as invalid. | You can ignore this error because DATASET is accepted as an alternative to FILE. If this problem has caused other options to be flagged as invalid, you might want to change DATASET to FILE to check that there are no other errors.
WRITEQ TS | The keyword TS is optional for this command. (This is for compatibility with earlier releases, and is not documented.) If you do not specify the TS option, the syntax checker assumes that the command is WRITEQ TD, and returns: `Command is ambiguous, 'TD' has been assumed` This causes other options to be flagged as invalid. | You can ignore this error because the syntax is correct. However, if you want to check the other options that were flagged as invalid you must specify TS to check that there are no other errors.
WEB ENDBROWSE | If using the HTTPHEADER keyword the SESSTOKEN keyword is optional, however if you omit it then the syntax check returns: `Command requires the option '<Expression>'` | You can ignore this error because the syntax is correct.
WEB READ | If using the HTTPHEADER keyword the SESSTOKEN keyword is optional, however if you omit it then the syntax check returns: `Command requires the option '<Expression>'` | You can ignore this error because the syntax is correct.
WEB STARTBROWSE | If using the HTTPHEADER keyword the SESSTOKEN keyword is optional, however if you omit it then the syntax check returns: `Command requires the option '<Expression>'` | You can ignore this error because the syntax is correct.

Terms of use | Feedback
This information center is powered by Eclipse technology. (http://www.eclipse.org)