One of the most common situations where a dequeue might seem appropriate is when you try to edit a program and receive the message:
IDADPSEP03-PGM xxxxxxxx is in use, please try later.
The fact is, the dequeue is appropriate only under a small set of circumstances if you receive this error. You need to ask yourself the following set of questions.
If you have a monitoring package such as CA SYSVIEW, you CAN see the outstanding enqueues by checking the major enqueue name "ADRPDCT".
If you do not have a monitoring package, then there is no easy and automated way to tell if an enqueue exists for that program. However, there is a good way to find out who might be using that program. The command DISPLAY INDEX SESSION tells you who is on the system and who is running programs.
From this, you can determine who is in CA Ideal but not currently running programs. Check whether any of these people are editing the program.
You can also check whether the program's identification component shows that it was recently updated. The indicated person might still be editing the program.
If your answer to this question is yes, then the message you are receiving is valid and you should not dequeue.
If your answer to this question is no, then continue to the next question.
You should be able to tell if an asynchronous online compile is currently being done through one of the following:
If there is a task with the SAST transaction, check the terminal ID. Find out who is at that terminal and see if they are compiling that program. Also check whether any batch compiles for this program are being done.
If your answer to this question is yes, then the message you are receiving is valid and you should not dequeue.
If your answer to this question is no, then continue to the next question.
First, find out if this CA Ideal environment has its own MUF (Multi‑User Facility) and its own set of VLS libraries.
If multiple CA Ideal environments are sharing MUF and VLS libraries, then this question is not an issue and you can continue to the next question.
If your CA Ideal environments are completely separate and a program of the same name (in the same system) does exist in another CA Ideal environment, then check your enqueue characters (QCODE). The QCODE is what makes your enqueue names unique between CA Ideal environments.
Since enqueues are done at the operating system level, identical QCODES in multiple regions enqueue programs with the same name (in the same system) in all regions where the QCODE is the same. To check your QCODES, issue the following command in CA Ideal:
@I$SCF PGM=SC00OPTS OFF=8
Offset 8 in the program SC00OPTS tells you what your QCODE is for this environment. Issue the same command in all your CA Ideal environments and note the QCODE. If your environments are completely separate, you need to make the QCODE unique among all your CA Ideal environments.
If your answer to this question is yes, then check your QCODEs. Do not issue the DEQUEUE command.
If your answer to this question is no, then continue to the next question.
Once again, make sure that nobody is currently editing or compiling this program.
If your answer to this question is no, then call CA Ideal Technical Support for further assistance.
If your answer to this question is yes, then you are safe to dequeue the program. Issue the following command:
DEQUEUE PROGRAM xxxxxxxx VERSION nnn SYSTEM sys
You can find the syntax for this command in the Command Reference Guide.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|