EJCK - PDS not found error



All other tools like QACenter, Strobe, Endevor, Telon, APAS, Scheduler, Auditor, DATA-XPERT, CoolGen, Intertest, AdvantageGen, COBTEST etc.

EJCK - PDS not found error

Postby 20sam13 » Wed Jul 10, 2013 9:09 pm

Here I go, at my shop we use the CA tool EJCK for our JCL checker. Works "great", but I have come across an issue that makes absolutely NO sense (see code block):

CAY6000 1 STATEMENT FLAGGED IN JOB "I5701A7P" MAXIMUM SEVERITY WAS 8

CAY6000 1 STATEMENT FLAGGED  WITH SEVERITY 8
CAY6000 NO ERRORS WERE SUPPRESSED

LINE # LABEL#  SV MSG. ID. ERROR MESSAGE TEXT
====== ======  == ======== ============================================

000090 .AAAFK   8 CAY6079E DATA SET
                           "OMDC.T.I578877.GDT.GTI.CA7P.CONADP.TC5T11
                            SPECIFIED AS OLD OR SHR, BUT CANNOT BE
                           FOUND


The PDS in question is only 41 characters in total length.

If i try to browse it using 3.4 for the PDS in question: OMDC.T.I578877.GDT.GTI.CA7P.CONADP.TC5T11
TSO reports "No Data set names found"

If I try again by starting at the far right, deleting one character and replacing with a *
TSO reports "No Data set names found"

If is NOT until I shorten the PDS name to: OMDC.T.I578877.GDT.GTI.CA7P.CONADP does TSO display a list of DSNs I expect.

Even if I try to submit the JCL, it errors on the first step, with a dataset not found, see code:


09.54.27 JOB21969  -STEP0020 STPR0020 FLUSH      0      0       .00       .00
09.54.27 JOB21969  IEF453I I5701A7P - JOB FAILED - JCL ERROR - TIME=09.54.27



Here is the JCL code block in question:


 20 XXSTPR0020 EXEC PGM=SORT                                                00751306
    XX*                                                                     00751403
 21 XXSORTIN DD DSN=&DATAIN.,                                               00751507
    XX          DISP=SHR                                                    00751603
    IEFC653I SUBSTITUTION JCL - DSN=OMDC.T.I578877.GDT.GTI.CA7P.CONADP.TC5TC10,DISP=SHR



Here is the JCL output showing the error message:


IEF373I STEP/STPR0010/START 2013191.0954
IEF032I STEP/STPR0010/STOP  2013191.0954
        CPU:     0 HR  00 MIN  00.00 SEC    SRB:     0 HR  00 MIN  00.00 SEC
        VIRT:     4K  SYS:   316K  EXT:        4K  SYS:    11028K
IEF212I I5701A7P STPR0020 STEP0020 SORTIN - DATA SET NOT FOUND
IEF272I I5701A7P STPR0020 STEP0020 - STEP WAS NOT EXECUTED.



Any thoughts?

This is the VERY FIRST time I have encountered this kind of an issue with DSNs of 41 or 42 characters.

Thanks!


PS... the [size=xx][/size] tags only work when outside of a block.
20sam13
 
Posts: 17
Joined: Fri Feb 15, 2013 8:44 pm
Has thanked: 0 time
Been thanked: 0 time

Re: EJCK - PDS not found error

 

Re: EJCK - PDS not found error

Postby NicC » Wed Jul 10, 2013 9:17 pm

Thought 1: the dataset does not exist
Thought 2: the dataset exists but is not cataloged.
You cannot change size within code blocks because it is fixed.
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: EJCK - PDS not found error

Postby 20sam13 » Wed Jul 10, 2013 9:19 pm

Well yes and yes... I fat fingered a substitution variable that builds a PDS name and thus it could not be found...

Go figure!!!
20sam13
 
Posts: 17
Joined: Fri Feb 15, 2013 8:44 pm
Has thanked: 0 time
Been thanked: 0 time

** SOLVED! Chair to keyboard interface error

Postby 20sam13 » Wed Jul 10, 2013 9:20 pm

** SOLVED! Chair to keyboard interface error
20sam13
 
Posts: 17
Joined: Fri Feb 15, 2013 8:44 pm
Has thanked: 0 time
Been thanked: 0 time

Re: EJCK - PDS not found error

Postby BillyBoyo » Wed Jul 10, 2013 11:51 pm

Not the "S" was it? Thanks for letting us know.
BillyBoyo
Global moderator
 
Posts: 3804
Joined: Tue Jan 25, 2011 12:02 am
Has thanked: 22 times
Been thanked: 264 times

Re: EJCK - PDS not found error

Postby 20sam13 » Thu Jul 11, 2013 12:49 am

Correct!!!

Was: TC5T11
Should have been: TS5T11

Just could not believe it....
20sam13
 
Posts: 17
Joined: Fri Feb 15, 2013 8:44 pm
Has thanked: 0 time
Been thanked: 0 time


Return to All Other Tools

 


  • Related topics
    Replies
    Views
    Last post