In ADSOBCOM, COMPILE FROM LOAD DIALOG fails with DC157001 INVALID INITIATING KEYWORD FOR COMMAND. How do you correct this error?

Products

• IDMS
• IDMS - Database
• IDMS - ADS

Issue/Introduction

In ADSOBCOM (CA ADS Batch Compiler), COMPILE FROM LOAD DIALOG fails with

100 !********************************************         

$                                                     

<E>   DC157001 INVALID INITIATING KEYWORD FOR COMMAND. STMT FLU

How do you correct this error?

Environment

Release: All supported releases.

Resolution

In our experience, the DC157001 INVALID INITIATING KEYWORD FOR COMMAND that flags the dollar sign ($ ) usually means the ADSOBCOM step is picking up an old IDMS release version of ADSOOPTI; perhaps from IDMS r17.0 loadlib and not from IDMS r18.5 which we have in the 18.5 CAGJLOAD loadlib. 

Add the 18.5 CAGJLOAD loadlib to the ADSOBCOM step. 

To verify what you have for ADSOOPTI, change the Steplib to your migration concatenation and run an IDMSLOOK for ADSOOPTI and see what loadlib it's being loaded from. 

Here's my 18.5 IDMSLOOK JCL: 
//**************************************************** 
//LOOK EXEC PGM=IDMSLOOK,REGION=2048K 
//STEPLIB DD DSN=<yourHLQ>.DBA.LOADLIB,DISP=SHR 
// DD DSN=<yourHLQ>.CAGJLOAD,DISP=SHR

 

// DD DSN=<yourHLQ>.CUSTOM.LOADLIB,DISP=SHR
//J1JRNL DD DUMMY 
//J2JRNL DD DUMMY 
//J3JRNL DD DUMMY 
//J4JRNL DD DUMMY 
//SYSLST DD SYSOUT=* 
//SYSUDUMP DD SYSOUT=* 
//SYSIDMS DD * 
DMCL=DMCL1850 
/* 
//SYSIPT DD * 
SET OPTIONS 1 THRU 72 
PROGRAM=ADSOOPTI 
/* 
============================================== 
Report: 
IDMSLOOK - OPSYS=z/OS Release 18.5 Service pack 0 tape GJI5 
PROGRAM=ADSOOPTI 

ADSOOPTI was loaded From STEPLIB DSN --> IDMS185.CAGJLOAD 
Entry Point Offset +0 - Nonreentrant - AMODE 24 - RMODE 24 
840 Bytes in Load Module ADSOOPTI loaded at 0006A000 

Module Offset Date Time FMID RMID 

ADSOOPTI +0 121202 0841 ~ZAPFMID RESERVE