How many requirements can be added for a single job on the DB.3.2 panel?
There is no limit to the number of requirements that can be added on the DB.3.2 screen. There is a limitation that has to do with the 'backward' pointer that is created/updated when requirements are added. For example, you add JOBB as a requirement for JOBA. There is a 'backward' pointer created -- you can see this 'backward' pointer by doing the command LCTLG,DSN=PRED.JOBB that shows the relationship. If JOBB is a requirement for more than 255 jobs, only the first 255 added are shown by this pointer. The backward pointer is only used for listing purposes and does not affect the attach or use of the requirement.
There is also a 255 limitation on the number of unsatisfied requirements for any job in the request queue...if a job has more than 255 unsatisfied requirements when it enters the queue, the number over 255 is what is shown in the MSTR RQMT field of the LQ. When the MSTR RQMT becomes 0, the job is ready for submission. In other words, if JOBA had 257 unsatisfied requirements when it comes into the queue, the MSTR RQMT field shows only 2 requirements. When any two of the 257 requirements are met, the job is posted for submission. There is an initialization file option of RQMT255= Y/N on the OPTIONS statement. RQMT255=Y says that if a job has more than 255 unsatisfied requirements when it enters the queue it will issue a WTO (CA-7.SFER-08), and build a special user requirement that has to be manually posted. This keeps a job with more than 255 unsatisfied requirements from being prematurely submitted.
As always, please contact CA Technologies support for CA 7 if you have further questions.