Error detected on device QPADEV0003

480 pts.
Tags:
AS/400
QINTER
Session Manager Subsystem
Hi,

When i am opening a new session , the QINTER job starts the new job named QPADEV007. Can anone suggest me the reason for error. I have pasted the JOBLOG below.

*****

Error detected on device QPADEV0003 that can be recovered.      Restore request failed. See message CPF5144.                    Restore request failed. See message CPF5144.                    Restore request failed. See message CPF5144.                    Last request to device QPADEV0003 failed.  See message CPF5144. Subsystem QINTER trying to recover work station QPADEV0003.     Unable to access device QPADEV0006 because error occurred.      Restore request failed. See message CPF5254.                    Restore request failed. See message CPF5254.                    Restore request failed. See message CPF5254.                    Last request to device QPADEV0006 failed.  See message CPF5254. Vary off completed for device QPADEV0006.                      

Subsystem QINTER varied off work station QPADEV0006.           Error detected on device QPADEV0006 that can be recovered.     Restore request failed. See message CPF5144.                   Restore request failed. See message CPF5144.                   Restore request failed. See message CPF5144.                   Last request to device QPADEV0006 failed.  See message CPF5144. Subsystem QINTER trying to recover work station QPADEV0006.   

*****************

COuld anyone help me out on the same.

Thanks in advance.

 



Software/Hardware used:
AS400

Answer Wiki

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

Tom,
When i am the first user to sign on the Virtual device name of the system has to be QPADEV001, but this is not so in my case, so i would like to know whats the problem?

Carreers:
Also i would like to know the carreer opportunity in As400(Iseries) in abroad and the salaries? Job sites have not a much option.

==========================================================

<i>i would like to know why those sessions are missing. </i>

Terminal devices with names like QPADEV0001 and QPADEV0002 are usually created automatically by the system.

A PC sends a terminal connection request to the AS/400. Part of the request is a description of the kind of terminal that should be used. The request might ask for a terminal that only supports screens that are 80 characters wide or it might ask for 132 characters wide. It might ask for a monochrome or a color terminal. It might ask for a number of different attributes by asking for a particular terminal type.

The AS/400 looks at the different QPADEV* devices that have been created to see if any of them are the right type. If it finds one, it checks to see if it’s in the proper state (varied on). If a device matches everything, then that device becomes associated with the interactive job. If it doesn’t find one, then it simply creates a new device, like QPADEV0003.

However, it will only automatically create new devices if the system configuration allows it. The most critical system value is QAUTOCFG to control if new devices are allowed to be created. Then there is QAUTOVRT to control the maximum number of devices to create automatically. (There are a few other possible elements, but those are what affect most sites.)

If the QAUTOCFG value is turned on but the QAUTOVRT limit has been reached, no more virtual devices will be created automatically.

So, the system can react differently. If it finds a device that is in the proper state but the terminal type doesn’t match, it will delete the device and create a new one with the same name. The new one will have a terminal type that fits the latest connection request. An existing device like QPADEV0001 might be a 132-character terminal device today; but it can be an 80-character device tomorrow. A connection request for a 132-char device will skip over QPADEV0001 tomorrow even if it connected to it today.

Also, different subsystems might allow the same devices to attach to them. Asd subsystems are started, they try to allocate all of the devices that are defined to be allowed in them. The last subsystem to allocate a device is the one that gets it.

But there are complications. The timing of allocations can be tricky. Two subsystems starting at the same time might process the list of devices at slightly different rates. Other elements such as auto-start jobs in one subsystem or memory pool assignments can cause the first subsystem to be a little slower. It might take longer for it to process devices. So even if it’s the first to start, it might be the last to try to allocate a particular device. Maybe that device will be allocated to MYQINTER instead on some days for almost random reasons.

Or maybe a PC user had trouble with a password. After trying a few times, the user profile was disabled and the device was varied off. QPADEV0001 won’t be available if it’s varied off.

In short, the sequence of devices can be practically impossible to predict. In order to guarantee a sequence, some significant programming is needed to ensure that all related events happen in the same order and all conditions start in the same state.

Usually it’s easiest simply to use explicitly named devices and let the auto-configured virtual devices get handled however the system needs to handle them.

Tom

Discuss This Question: 8  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
  • TomLiotta
    When i am opening a new session , the QINTER job starts the new job named QPADEV007. Why is that a problem? Devices named with the first letters "QPADEV" are generally virtual devices that are assigned automatically by the system. The next user to connect will get the first available virtual device that is in the proper state. The proper state should be "Varied on" though "Vary on pending" might work under some circumstances. What exactly are you trying to do? If you are trying to connect explicitly to such a device, the timing and technique takes some work. Tom
    125,585 pointsBadges:
    report
  • TomLiotta
    Because it's a "virtual" device assigned by the system, you can't really guarantee that you're going to get it without some significant programming. If you need a specific device, use a 'named' device that you can reliably specify. Use a device name other than the QPADEV* devices and assign authority to your device accordingly. Technically, you can possibly create a Device initialization exit program, but be extremely careful because this program can override normal system behavior. Errors in logic (or in interpreting the meanings of the parameter data structure values) can result in the system being opened to the world. I strongly recommend simply not using QPADEV* devices at all for users who require specific device names. Use some alternative names based perhaps on user profile names or initials. Tom
    125,585 pointsBadges:
    report
  • Splat
    One thing to check would be to see if the device description for QPADEV003 (and QPADEV006) are varied on. If nothing else, delete the objects - the system will recreate them.
    7,185 pointsBadges:
    report
  • TomLiotta
    ...see if the device description for QPADEV003 (and QPADEV006) are varied on. Why? That is, if I read it correctly, he doesn't want either of those. If he's the first to sign on, he only wants QPADEV0001. The others should be irrelevant. They shouldn't show up as being involved in his connection attempt at all. The problem is that the system will give him the first available device it finds that matches the characteristics from his connection request and that is in the appropriate state. For basic auto-configured virtual devices, that can be tricky to guarantee. It's not clear why QPADEV0001 should have special meaning. It's one of the devices that the system expects to throw away (and recreate with new attributes) whenever it decides to. Tom
    125,585 pointsBadges:
    report
  • Splat
    I was focused on the initial question & didn't pay enough attention to the bit about QPADEV0001.
    7,185 pointsBadges:
    report
  • TomLiotta
    Yeah, I'm still not certain I understand why there's a problem at all. Perhaps if we knew what the 'business objective' was, we could suggest alternatives. Tom
    125,585 pointsBadges:
    report
  • as400dev
    Previously ,when i am the first user to Sign on the device name would be - QPADEV0001, for the next screen i ll get as QPADEV0002. But this is not so now, i would like to know why those sessions are missing. If the system needs to give him the first available device , so why it does not starts with 001. When i execute the WRKJOB JOB(QPADEV0001) all the jobs are in OUTQ, so that shoulnt be a problem. There is no business objective. I would like to clarify why this happens.
    480 pointsBadges:
    report
  • as400dev
    Thanks TOM You gave a very nice Explanation. You rocks. Thanks a lot.
    480 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