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

Need some information on U11RMS


IBM Mainframe Forums -> CA Products
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Geethanjali

New User


Joined: 24 Jan 2008
Posts: 6
Location: Chennai

PostPosted: Thu Jan 24, 2008 11:07 am
Reply with quote

HI,

I think u all know about U11RMS,which takes care of deleting datsets and allocating correct GDGs in a Job.

Normally U11RMS will be executed with TYPRUN=P

Say, A Job abends

Then while restarting it,the U11RMS will be executed with TYPRUN=R(Restart mode) and the output datasets and GDGs which has been created in the first run will be deleted in the restarted job.

My problem is,

I dont want the restarted job to delete my output GDGs.

Is there any way to retain those datasets?

Actually,I have one dataset which will be created when the job abends.I am having the reason for the abend in this dataset(GDG version)

But when the job was restarted U11RMS is deleting that GDG version.

I tried with DISP=(NEW,CATLG,DELETE) and DISP=(NEW,CATLG,KEEP)

but there is no difference.

My final question,

Is there any way to retain that GDG version even after restarting the job with U11RMS TYPRUN=R ?
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Thu Jan 24, 2008 5:00 pm
Reply with quote

Geethanjali wrote:
Is there any way to retain that GDG version even after restarting the job with U11RMS TYPRUN=R ?
Rename the generation (version) created in the un-successful JOB & use TYPRUN=F.
Back to top
View user's profile Send private message
Geethanjali

New User


Joined: 24 Jan 2008
Posts: 6
Location: Chennai

PostPosted: Thu Jan 24, 2008 6:05 pm
Reply with quote

I cant restart the job with TYPRUN=F,

If it is restarted then TYPRUN will be R

As of now I am renaming the GDG,

Can I get some other solution?

Is there any thing to do with DISP?
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Tue Jan 29, 2008 4:31 pm
Reply with quote

TYPRUN=F means a "Fresh run", as if there was no logical previous run today..it's not a restart. I didn't get what do You want to convey when You say..
Quote:
I cant restart the job with TYPRUN=F


In my system I've a JOB which removes the affect of such a JOB we call it UARTS...not sure if it is used across systems. Check out for such a JOB in your system, that can be other option.
Back to top
View user's profile Send private message
Geethanjali

New User


Joined: 24 Jan 2008
Posts: 6
Location: Chennai

PostPosted: Tue Jan 29, 2008 5:36 pm
Reply with quote

Its a live system and we cant live our options or parameter for the jobs.

Whenever a job is restarted then the TYPRUN is R only.

That is what I meant by 'I cant restart the job with TYPRUN=F'

Did u get the condition?

I want to know is there anything to do with DISP? or
Can anything be done in the job without touching U11RMS parameters?

(Note:I cant change anything in the job if it is abended (As it is live),just some other team will restart the job.I am searching for a solution to enhance the job and to retain the deleted dataset.)
Back to top
View user's profile Send private message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 194
Location: India

PostPosted: Wed Jan 30, 2008 5:40 pm
Reply with quote

Geethanjali wrote:
Its a live system and we cant live our options or parameter for the jobs.

Whenever a job is restarted then the TYPRUN is R only.

That is what I meant by 'I cant restart the job with TYPRUN=F'

Did u get the condition?

I want to know is there anything to do with DISP? or
Can anything be done in the job without touching U11RMS parameters?

(Note:I cant change anything in the job if it is abended (As it is live),just some other team will restart the job.I am searching for a solution to enhance the job and to retain the deleted dataset.)


this is not solution but might be alternative..
you add one more step after the gdg creation. make sure when ever that gdg version created it copied to the next ddname which you are going to catalogued..then if the job fails and you restarted the dataset which is catalogued will not be deleted.

not sure ..just tried to answer ...
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Mon Feb 04, 2008 7:56 pm
Reply with quote

Hi,

I didn't get one thing..if this...
Geethanjali wrote:
Its a live system and we cant live our options or parameter for the jobs.
is not possible...then how can You try this option?
Quote:
I want to know is there anything to do with DISP?
Back to top
View user's profile Send private message
Geethanjali

New User


Joined: 24 Jan 2008
Posts: 6
Location: Chennai

PostPosted: Tue Feb 05, 2008 9:20 am
Reply with quote

If something works with DISP then we will inform the customer and if they are fine with the changes then we can implement it.
Back to top
View user's profile Send private message
HappySrinu

Active User


Joined: 22 Jan 2008
Posts: 194
Location: India

PostPosted: Tue Feb 05, 2008 12:21 pm
Reply with quote

Anuj D. wrote:
Hi,

I didn't get one thing..if this...
Geethanjali wrote:
Its a live system and we cant live our options or parameter for the jobs.
is not possible...then how can You try this option?
Quote:
I want to know is there anything to do with DISP?


you are right man, but i thought you could create test jobs in try this option. any way it's just my suggestion..

Thanks icon_smile.gif
Back to top
View user's profile Send private message
Anuj Dhawan

Superior Member


Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India

PostPosted: Tue Feb 05, 2008 10:35 pm
Reply with quote

In Your first post You say that if JOB get abended then on restart it deletes the previous GDG. Well, as far as I know U11RMS does not delete any GDG on restart instead it treats the new GDG (generation) as the current generation, which might have already been updated by some program, which might lead to wrong outputs in re-run (restart). I'm sure it's not the answer You are searching for, however, we can not play with DISP for this problem I think.
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 -> CA Products

 


Similar Topics
Topic Forum Replies
No new posts Capturing Job Execution Information All Other Mainframe Topics 3
No new posts Extract all the TWS scheduler informa... IBM Tools 1
No new posts Table Information - DB2 DB2 1
No new posts Remove additional information in SUPE... TSO/ISPF 10
This topic is locked: you cannot edit posts or make replies. Control-M Information. CLIST & REXX 1
Search our Forums:

Back to Top