Return Code 01 - INVALID REQUEST COMMAND

CA Datacom/DB Return Codes › Return Codes › Return Code 01 - INVALID REQUEST COMMAND

Return Code 01 - INVALID REQUEST COMMAND

Reason:

The command in the Request Area is not spelled correctly or is not valid in the way it is being used for the environment.

If you are using CA Datacom CICS Services, a CA Datacom/DB request was detected which is not permitted in an online request.

If you are using the CA Datacom IMS/DC Services, the current application program issued a CA Datacom/DB OPEN or CLOSE. However, these CA Datacom/DB commands are not valid in a program using CA Datacom IMS/DC Services. CA Datacom IMS/DC Services handles the OPEN/CLOSE functions through the internal management.

Action:

If you are using the CA Datacom IMS/DC Services, remove the OPEN or CLOSE from your application program. See the following internal return codes for details.

Return Code 01 Internal Return Codes

Dec	Hex	M	B	Explanation	User Response
001	01	N	N	CA Datacom CICS Services error. CA Datacom CICS Services detected an invalid CA Datacom command in DCCTPPR.	Fix the application that issued the bad command. If not known, do the following steps to isolate and determine the problem, if it is reproducible: DBOC TRACE,RCBYPASS=00 <-enter> DBOC TRACE,RCBYPASS=14 <-enter> DBOC TRACE,RCBYPASS=91 <-enter> DBOC TRACEON RERUN the test or wait a while DBOC INQ=TRACE (this command should display the bad command)
032	20	S	N	If using DBNTRY as an entry point, the command name is misspelled. If using CBLDBMS or DATACOM as an entry point, either the command name is misspelled or the command is not supported. Commands not supported through CBLDBMS or DATACOM include the following: CNTKY CNTTB GETPS GSETP INQIN LOCBR LOCKL REDBR RDUBR REDKL RDUKL SELCN SELFR SELNR SELPR SELSM SELST The request area address is the second parameter for the DBNTRY entry point. This request area began with a numeric value (that is not a valid command), and did not begin with a C'1RQ1'. Therefore, it was an invalid request area. The older entry points, DBLDBMS and DATACOM, do not support the 1RQ1 with one of these entry points. One or more of the reserved 1RQ1 input fields were not set to binary zeros.	If the command name is misspelled, correct the spelling. If the command is not supported through your entry point, revise the program logic.
033	21	N	N	You issued a CA Datacom/DB command which is not allowed. When RRS=YES is specified in the DBURINF User Requirements Table macro, the following are not allowed: COMIT, LOGCP, LOGCR, LOGTB, and ROLBK record-at-a-time commands COMMIT and ROLLBACK SQL statements DEQUE commands that CA Datacom CICS Services issues	When you have a RRS=YES User Requirements Table: Issue an Application_Commit_UR command for a commit. Issue an Application_Backout_UR command for a rollback. The Application_Commit_UR and the Application_Backout_UR commands communicate with RRS, and RRS coordinates a two-phase commit across all resource managers.
034	22	N	N	An attempt was made to execute a GSETP or GETPS command using the Any Parent table or the SQL LOCK TABLE statement using the Any Parent table. These are not supported.	Change the program so it does not use the Any Parent table.
175	AF	S	N	A SQLMODE command is being attempted against a MUF without the SQLMODE option selected.	Change the MUF startup options to support SQL Manager.
255	FF	N	N	This is not an error. It is a place-holder in the 1RQ1 request area to avoid confusion with the return code field at its proper offset in the 1RQ1 request area. For more information about the 1RQ1 request area, see "Large Keys and the 1RQ1 Request Area" in the Programming Guide.	Not an error and no user response is required. For return code checking, look at the proper offset in the 1RQ1 request area.