John McKown stated: > So, to be able to track the relationship between an MVT job > and a HASP job, the name of the job while executing had to > be unique.
No. There was no confusion. HASP knew quite well which JOB was running in an initiator (that is, under a certain task). The real problem was that there was no A= operand on the C[ancel] command. If multiple JOBs with the same name were allowed to initiate, there was no way to cancel a specific one, since the CSCB (the namespace for the Cancel command) created for each one was identical (had the same JOB name). If you made a mod to HASP that would allow identically named jobs to run and you then tried to cancel one of them using the operator C[ancel] command, the JOB that would actually get canceled was the first one on the CSCB chain. To prevent this, HASP simply didn't allow multiple jobs to initiate with the same JOB name. That particular situation was rectified with the addition of the A= (ASID) parameter to the Cancel command so that it was possible to specify which specific JOB by that name to cancel, but JES2 still enforced this original restriction until long after. -- WB ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
