IBM Mainframe Forum

Hello All,
Looking for guidance with the below stated issue:

One of the CLIST member, invoked by PANELS is throwing below error, while executing the IEBDG
Error message:
IEC130I XXXXXX : DD STATEMENT MISSING
***

Where in XXXXXX is the truncated TSO ID of the USER. The TSO ID gets truncated for the first character and recognized only as SIX Characters when this error is thrown. (Example: TSO ID as in ABCDEFG , is getting truncated as BCDEFG)

CLIST statements are as followed: Allocates WORK datasets and executes IEBDG to build NULL RECORDs in the work files.

ALLOC F(WORK1) DA('&SYSUID..WORK1') NEW CATALOG SPACE(3 1) TRACKS -
USING (DCB1) UNIT(SMS)
ALLOC F(WORK2) DA('&SYSUID..WORK2') NEW CATALOG SPACE(3 1) TRACKS -
USING (DCB2) UNIT(SMS)
FREE F(SYSIN OUT1 OUT2)
ALLOC F(OUT1) DA('&SYSUID..WORK1') SHR
ALLOC F(OUT2) DA('&SYSUID..WORK2') SHR
ALLOC F(SYSIN) DA('AAAA.BBB.CCLIB(XXXXXX)') SHR
IEBDG

SYSIN contents are as follows:
DSD OUTPUT=(OUT1)
CREATE INPUT=SYSIN
$$$E
END
DSD OUTPUT=(OUT2)
CREATE INPUT=SYSIN
$$$E
END

My observation:
1. the above said error is thrown during the execution of IEBDG utility, which takes OUT1, OUT2 and SYSIN as inputs.
2. The utility IEBDG helps in building the records into the work files. In this case, its just helping us to build a NULL Record.
3. The syntax involved in IEBDG utility SYSIN cards are found to be good and works good in batch execution also.
4. Most importantly this CLIST is working for few users and only specific Users are getting the above mentioned error.

I believe the issue might be with the USER PROFILE, where in the USER'S TSO ID is getting truncated. Looking for guidance from the experts.
Wish I can share any other information if needed. Thanks in advance.

IEBDG is a batch program, not a TSO command. TSO commands are called using a different interface than a batch program. Try changing the IEBDG line to

CALL *(IEBDG)

The use of the TSO interface may be confusing IEBDG.

By the way, the IEC130I message is an MVS message, not a TSO message. The XXXXXXXX is supposed to be a DD name, copied from the DCB data area of a DCB IEBDG is trying to open. XXXXXXXX is not a TSO userid, unless the DD name in the DCB is also a TSO userid.

Finally, MVS does not "throw" anything, ever, unless it's confusion in the minds of people trying to use it.

These users thanked the author steve-myers for the post:

NJ_quest (Thu Nov 30, 2017 6:24 am)

Thank you Steve! This resolved the issue.

Well said-
"Finally, MVS does not "throw" anything, ever, unless it's confusion in the minds of people trying to use it."