Capture *LDA data on job load

[adrotate group=”3,4,8″]
One feature we have been trying to provide in our JobQGenie product is the ability to capture the *LDA data when a job is loaded to the job queue. This data is generally used by older RPG programs as a method of passing in parameters. I say older but I was surprised at just how many use this feature and some are not really that old…

When we replicate the job queue content to the remote server and store it for re-submission the *LDA data was not captured anywhere, this meant those users who used LDA’s for passing in program data could not be sure their jobs ran as expected because the parameter data was missing.

Another problem which falls into the same category is the library list which is stored by the OS every time you submit a job the system will run that job with the same library list as you have at the time of the submission (unless you are using jobd’s of course). JobQGenie has always been able to store the library list data that the job ran with, but until now it had to rely on the user ensuring they used JobD’s for setting the library list.

Now we have the ability to capture both as soon as the job is loaded and can store this data with the other job information just in case it is needed to re-submit the job again. This means you can be sure the job runs on the target system in the same environment it would have run on the source system.

If you are running any kind of HA software we would encourage you to get in touch with us, if you have a system failure being able to re-submit your jobs again could be the deciding factor between being able to recover properly or not! Even if you are doing planned role swaps, if the job queue content is ignored because you feel the HA software package you have is looking after it, you could be in for a rude awakening. More than once we have heard people comment on how surprised they are that the HA tool they are using does not support job queue content replication. Also remember replication of the job queue object does not replicate its content…

The cost is minimal in comparison to what you have already spent on your HA solution, like they say “why spoil the ship for an h’pth of tar!” or even a “stitch in time saves nine!”. Don’t wait until its too late…

We look forward to your calls… 🙂

Chris…

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.