Device is vary on pending when AS/400 job is running

175 pts.
Tags:
AS/400
AS/400 jobs
My device is vary on pending when job is running, we have a system where user job is looping under one device description.
QVIRCD0017        ACTIVE
TUOLST_S9       VARY ON PENDING       TUOLST_S9   SETUMGE     154582
Can someone suggest what needs to be done? Since every time I need to end his job and it take high CPU as well. Thanks & Regards Deepak


Software/Hardware used:
v7r1
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 6  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.
  • TheRealRaven
    Can someone suggest what needs to be done?

    Before anything can be suggested, we need to know the error that took the device down. From the error, we might help with next steps.

    Be sure to include message IDs.
    35,650 pointsBadges:
    report
  • ToddN2000
    What does the device have to job that is running? Was this job running and the device ended abnormally? How are the devices configured and can you have multiple signons for the same user? Can you provide more details on how the error condition started?
    133,740 pointsBadges:
    report
  • deepakt1

    Hi,

    in the device ,qry is runs and only one sign on is allowed per user on the device. i see also device goes on very on pending after user runs the jobs through this.below is the error i see in the logs

    User ID and address SETUMGE  not in System Distribution Directory.
    Session stopped by a request from device TUOLST_S9.              
    Input or Output request failed.  See message CPF5140.            

     

     

    175 pointsBadges:
    report
  • ToddN2000
    You say "User ID and address SETUMGE not in System Distribution Directory". That means they need to be added to the system using the ADDDIRE. Check first to be sure using the WRKDIRE command.
    133,740 pointsBadges:
    report
  • TheRealRaven
    Most likely, if it's some kind of query, invalid characters are being output to the display. That causes a display failure, and the job disconnects from the display device.

    As for the error messages (which were not shown with message IDs), it's very likely that an old application is still using the old, almost obsolete /QDLS file system. That application should be updated to stop using "folders and documents" and to start using "directories and streamfiles" instead. When that's done, there won't be any need for enrollment in the old system directory.

    The application should be updated before IBM decides to stop supporting it completely. Most functions were removed some 20 years ago.
    35,650 pointsBadges:
    report
  • ToddN2000
    That is the joy of maintaining legacy code. Sometimes we have no choice or we nullify the support for the software vendor.
    133,740 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.

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

Following

Share this item with your network: