Performance issues regarding merging libraries

575 pts.
Tags:
AS/400 performance
I received an email yesterday from a reader who has a big task. She is working with a hospital to merge three different libraries into one using AS/400. "One Hospital is going for data merger of three different libraries to one single library including some data mapping and conversion. There are lots of programs written for conversion of data to single library. But we are facing performance issue as converting billions of records takes time and CPU usage goes high, resulting in slowness of application. We can implement the concept of multithreading, but monitoring each job for its conversion may become a big task. What should we do?"

Answer Wiki

Thanks. We'll let you know when a new response is added.

It look like this project is pretty huge so in that case, I would probably ask to create a special subsystem with a specific shared pool insulated from the one used by QBATCH so each of them would have their individual memory and CPU specs so they wont disturb the other one while running Monster jobs.

If you do so, dont forget to start your sub system at IPL time in your QSTRUP pgm.

Have Fun !

__________________
DanTheMan

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Karank
    yes , time is factor here also.......... we have to prioritize the job...we have to assigne less than 10 priority for them.......if we set the priority to 70 then it will get delayed or will take longer time........ May be we can have another solution other than multithreading which is our last left option >
    55 pointsBadges:
    report
  • TomLiotta
    we have to assigne less than 10 priority for them You do not want to assign "less than 10" priority. You probably don't want to assign less than 11. At a "less than 10" priority, the job will become difficult to control if any problem arises. Priorities below 10 should be reserved for system tasks and priority 10 should probably be reserved for the system console itself. All application processes should be above 10. Tom
    125,585 pointsBadges:
    report
  • Splat
    Let me second Tom. Under no circumstances should any user job be given a priority of 10 or less. Doing so deprives the system of resources necessary to support the job. Last time I saw someone do that the system locked up, necessitating a force power down and causing the loss of much of a day's work.
    7,235 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following