EJESLNK not working for me but not in Integration.

vrmadduri · Posted: Tue Dec 11, 2012 9:09 pm

Hello,

The utility was working for me in the development region where I'm executing the utility in the job names starting with my userid. But I'm getting the following message in the Integration region: "EJES155 The string could not be located on any row of this display" and not extracting spool output of the executing job to dataset.

Thanks,
Venkat

Robert Sample · Posted: Tue Dec 11, 2012 9:20 pm

vrmadduri, did you notice you are replying to a thread last updated MORE THAN 4 YEARS AGO? Also, would not the user id being used for integration testing be different than your user id?

dick scherrer · Posted: Tue Dec 11, 2012 10:20 pm

Hello and welcome to the forum,

Your question has nothing to do with the topic you replied to (yes, they are both about EJES, but not at all the same issue). Also, you replied to a topic that has been dormant for more than 4 years.

Your question has been split into a new topic, but i do not beiileve it hs a rexx / clist question. Please correct me if i'm wrong.

When these jobs are run in the Integration environment which jobname(s) and user-id(s) are used (as Robert asked).

vrmadduri · Posted: Tue Dec 11, 2012 10:50 pm

Hello Robert and Dick,

Sorry it was my first post.

I don't know the userid who was submitting the job in Integration, but the job name was MM$OTICE.

//EJESLNK.EJESIN DD DATA,DLM=$$
JNAME MM$OT*;SORT TIME D;STATUS
F MM$OTICE FIRST
:E
ECHO ON
ECHO OFF
$$
/*

They got the following message.

EJES290 TIME sort has been enabled for this function
EJES155 The string could not be located on any row of this display
STATUS - 18141S- 0X- 0W- 0H- 0T- 0 Records- 0 Lines- 0 Pages ---------------------------------------------------------- Row 0 of 0
Cmd JobName JobID Status Process StepNum StepName JP MaxComp Records Lines Pages Pos H-OSE W-OSE B-OSE T-OSE Own
--- -------- --------/-------- -------- ------- -------- -- -------- ---------- ---------- -------- --- ----- ----- ----- ----- -->
********************************************************* Bottom of Data **********************************************************

Thanks.
Venkat

dick scherrer · Posted: Tue Dec 11, 2012 11:17 pm

Hello,

Akatsukami · Posted: Tue Dec 11, 2012 11:25 pm

Akatsukami · Posted: Tue Dec 11, 2012 11:41 pm

Playing with my (OK, my client's

) (E)JES system shows the error: the job name, even if partial, should not be wildcarded. Specify:

vrmadduri · Posted: Wed Dec 12, 2012 12:46 am

Hi,

I tried wild card in development region and it worked. The Integration rundeck has USERID=MMNOT coded in the JOB statement and job name was MM$OTICE. Is this causing the EJESLNK not finding any jobs in the spool?

Thanks,
Venkat

dick scherrer · Posted: Wed Dec 12, 2012 12:54 am

Hello,

Did you try in Integration without the wildcard?

What happened?

vrmadduri · Posted: Wed Dec 12, 2012 12:57 am

I didn't got the necessary extract without wild card in development.

Thanks,
Venkat.

Akatsukami · Posted: Wed Dec 12, 2012 12:59 am

vrmadduri · Posted: Wed Dec 12, 2012 1:03 am

Robert Sample · Posted: Wed Dec 12, 2012 2:03 am

vrmadduri, this is definitely one of those issues that you need to discuss with your site support group. The job name may be different between development and integration -- and the change could be done via a JES exit so you would not necessarily know about the change. Another possibility is that if the development and integration areas are running in different LPARs of your machine, it is quite possible that the wild card character for (E)JES in development is NOT the wildcard character in integration - -and only by talking to someone working at your shop could you resolve such an issue. There are other possible reasons for the results you got, but the bottom line is that unless you talk to people working at your site, you are unlikely to resolve your issue.

vrmadduri · Posted: Wed Dec 12, 2012 3:07 am

Thanks Robert. I'm working with Integration region guys regarding the issue, but they don't know about the EJESLNK utility and how it works.

Thanks,
Venkat.

prino · Posted: Wed Dec 12, 2012 3:31 am

vrmadduri · Posted: Tue Dec 18, 2012 2:47 am

Hello,

I got the required extract in Integration, when I changed the EJESLNK step override as follows:

//EJESLNK.EJESIN DD DATA,DLM=$$
SRESET
J=MMNOT$CE;SORT TIME D;STATUS
ST
F ‘MMNOT$CE’ FIRST
:E
NOP
$$
/*

Thanks,
Venkata.