IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Trying to get the list of jobs from Beta 92 using a JCL.


IBM Mainframe Forums -> JCL & VSAM
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
janaonline

New User


Joined: 13 Dec 2007
Posts: 11
Location: USA, California

PostPosted: Wed Sep 29, 2010 1:15 am
Reply with quote

Well, Before going to the point that am looking, let me explain the process that is happening. There are around hundreds of JCL that is getting executed on a daily basis but it has been designed to have internal reader to trigger the next job. In the aspect of job execution that was fine. But when we think about return code validation we need to check eacj and every job in beta. Thats is a little tedious one to do on a regular basis.

I have a JCL where it searches the BETA 92 and it will load the output in the file. The output contains, JESMSGLG,JESJCL and JESYSMSG.

//SYSIN DD *
BFIND
SDATE(09/27/10)
STIME(18:00:00)
PDATE(09/28/10)
PTIME(12:00:00)
JOBNAME(ABC123)
JOBID(*)
NETID(*)
GROUP(*)
OPERATOR(OR)
OPTIONS(ALL)
SCOPE(BOTH)
MESSAGE(LONG)
RELOAD(NO)
MIXEDMODE(NO)
SLINE(0)
PLINE(0)
STRING2( )
STRING1( )



My request:
I wanted to display only the details like (Jobname Job ID Date Time Status Error ). If someone is aware of that, i would really appreciate if you could help in finishing this.

Thanks for you time.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Wed Sep 29, 2010 1:27 am
Reply with quote

Hello,

Not really what you asked, but why does jobN submit jobN+1 thru the internal reader if jobN was not successful? The process should stop with the failed job - should it not?

You have shown a "sysin" but what is the rest of the jcl for this step? Very few people will be able to relate with only some sysin parameters to look at (unless they know completely what you are using - and most will not).

Quote:
I wanted to display only the details like (Jobname Job ID Date Time Status Error ).
If these jobs are run "normally" and have sysout info in the spool after execution, you might use sdsf in batch to do what you want. There are multiple topics about sdsf in batch in the forums. There is a forum SEARCH feature above in the blue bar.
Back to top
View user's profile Send private message
Akatsukami

Global Moderator


Joined: 03 Oct 2009
Posts: 1788
Location: Bloomington, IL

PostPosted: Wed Sep 29, 2010 1:30 am
Reply with quote

As Beta 92 is a proprietary process analysis system not possessed by every shop, would it not be better to approach Beta Systems, either directly or through the appropriate support analysts in your shop?
Back to top
View user's profile Send private message
janaonline

New User


Joined: 13 Dec 2007
Posts: 11
Location: USA, California

PostPosted: Wed Sep 29, 2010 2:00 am
Reply with quote

dick scherrer wrote:
Hello,

Not really what you asked, but why does jobN submit jobN+1 thru the internal reader if jobN was not successful? The process should stop with the failed job - should it not?


That is totally understandable and i absolutely support your point. The problem is, the person who runs and maintains the region is from external vendor and my management was accepted to this setup and at this point i cannot do anything. Since already it started and going on..

Quote:
You have shown a "sysin" but what is the rest of the jcl for this step? Very few people will be able to relate with only some sysin parameters to look at (unless they know completely what you are using - and most will not).


//SEARCH EXEC PGM=BSS01RFF,REGION=0M,
// PARM=('S=92,B01LST=A1,B92LST=J1',
// 'PGM=B92FFIND')
//*
//*
//B92DEF DD DUMMY
//*
//SFFPARM DD DISP=SHR,
// DSN=SYS9.BETA.PARMLIB
//*
//SFFFDUMP DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//OMSPRINT DD SYSOUT=*
//B92LOG DD SYSOUT=*
//*
//SYSIN DD *


Quote:
I wanted to display only the details like (Jobname Job ID Date Time Status Error ).
If these jobs are run "normally" and have sysout info in the spool after execution, you might use sdsf in batch to do what you want. There are multiple topics about sdsf in batch in the forums. There is a forum SEARCH feature above in the blue bar.[/quote]

I could certainly validate it in spool, but i have hundreds of jobs and jobs were routed to beta so i will not be able to check once the job is over.

The process that am trying to do is, by getting the list from beta i could maintain a daily status log of all these jobs.

Thanks a lot for your time.
Back to top
View user's profile Send private message
dick scherrer

Moderator Emeritus


Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix

PostPosted: Wed Sep 29, 2010 2:05 am
Reply with quote

You're welcome - good luck icon_smile.gif

As Akatsukami suggested:
Quote:
would it not be better to approach Beta Systems
They should be able to provide guidance. . .

d
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> JCL & VSAM

 


Similar Topics
Topic Forum Replies
No new posts Finding and researching jobs All Other Mainframe Topics 0
No new posts How to create a list of SAR jobs with... CA Products 3
No new posts Help in Automating Batch JCL jobs mon... JCL & VSAM 3
No new posts Submit multiple jobs from a library t... JCL & VSAM 14
No new posts Build dataset list with properties us... PL/I & Assembler 4
Search our Forums:

Back to Top