ljs job(xxxx) i command

[Legacy User]

in our shop

ljs job(xxxx) i

command provide last 10 runs information/history,  I would like to increase this to max 45 or at least

24 runs. 

Is there any harm in changing default value?  We don't want to crash ESP!! but like to have more history with single command from LMI view.

 

 

The command sent to the server is: ljs job(xxxx) i

JOB xxxx, OWNER NONE, 10 JOBS INDEXED, 10 MAX

 

Thanks

[Jonathan Calloway]

Have you tried using ltj as opposed to ljs?

[Legacy User]

Thanks Jonathan,

 

I think, LTJ command only works if job is name is 8 char?  we have lots of  Windows/Linux jobs which use longer name

when use LTJ option with longer name we  get  following error

ltj A1_ABCD_xxxxx i

ESPWSS900I STRING TOO LONG, A1_ABCD_xxxxx

ESPWSS000 -->

 

 Also,  with in ESP director view if we issue list job history command its provide only

10 MAX runs.

I am thinking may be some kind of default settings need to change but not sure if it will impact over all ESP performance or something.

 

THanks

[Lucy Zhang]

Hi Atif,

 

Increasing INDEX on LJS will increase the space usage on JOBSTATS file. So you may consider to allocate a larger JOBSTATS file and run CYBESUT8 more frequently to clean up this file. Other than that, there should be minor impact on the ESP performance.

 

Still when possible, history report is the recommended way to get historic information.

 

Hope this helps,

 

Lucy

[Lucy Zhang]

Also please make sure to select "CA Workload Automation ESP" in the subcategories, so that all ESP users can see it.

 

Thank you,

 

Lucy

[Legacy User]

Thanks Lucy,

 Can we use LTJ command or any similar command for distributed jobs ( job with longer than 8 char name ).

 

Thanks

[Lucy Zhang]

Hi Atif,

 

LTJ output is based on information from JOBINDEX file, the first 8 chars of the job name will be used as the key. So all jobs with same first 8 chars will be written to the same record. It's fine for mainframe jobs, but not good for distributed ones if they use >8 chars for their job names.

 

Hope this helps,

 

Lucy

[Legacy User]

Thanks for your help, would love to see more flexibility for distrub jobs...Thanks

[Lucy Zhang]

Hi Atif,

 

LJS is meant to avoid the limitation of LTJ command and it will work for distributed jobs if JTDT is set properly.

 

Is there anything that it doesn't meet your need?

 

Thank you,

 

Lucy

[Legacy User]

Hi Lucy,

Most of our users are using GUI/CA Workload Automation Workstation EE, I was looking into quick option to generate job hisotry with more than 10 runs.... without causing any trouble to ESP over all.

Job history option in CA Workload Automation Workstation EE only provide max 10 runs just like

ljs job(xxxx) i command at LMI.

 

LTJ commands looks good but not working when we have long job name, and this option is not available in GUI

 

Thanks for your help.

[Lucy Zhang]

Hi Atif,

 

You can add JINDEX on JOBSTATS file to get more than 10 entries on LJS output. Any reason that you want to see more than 10 entries on LJS? Note: you can use JOBPROF feature if you want to see the data related to a special run (weekly or monthly) of the job.

 

I don't see much difference on LTJ and LJS output. Are there any information you need that shows on LTJ but not LJS?

 

Thanks,

 

Lucy

[Legacy User]

Hello,

JOBPROF feature, that may be helpful.  No sure since i havent done my home work... will work on this option.

 

 We have some backups jobs  run longer once in week/month due to FULL backups,  and cause over due alerting so i want to investigate and alert differently depdendes on day of week/month.

List Job History option in ESP directore ( GUI ) is bit faster and quicker way..or LMI command ljs job(***) i.

 

 Having more than 10 list provide some kind of pattern,   and helpout

 

No i dont see much difference in LTJ and LJS output,  only problem LTJ not working out if job name is 8+ char long

 

Thanks

 

 

 

[Lucy Zhang]

Hi Atif,

 

Based on your description, JOBPROF and MAXRUNTIME use together should work for you. See "JOBPROF: Defining a Job Profile Name" on "Installation and Configuration Guide" and/or "Command Reference Guide" for more detail and examples.

 

For example:

JOB BACKUP

JOBPROF BACKUP.ALL ON('ANYDAY')
JOBPROF BACKUP.FRIDAY ON('FRIDAY')

JOBPROF BACKUP..MONTH ON('LAST WORKDAY OF MONTH')

MAXRUNTIME = AVGRUNTIME * 150 / 100

....

ENDJOB

 

So the weekly run and monthly run have their own profiles which contains different average runtime. 

 

Hope this helps,

 

Lucy