In a recent note, Edward E. Jaffe said:
> Date: Tue, 30 Aug 2005 16:13:07 -0700
>
> Paul Gilmartin wrote:
>
> >... We're using a private integrity facility that
> >issues an exclusive ENQ on SYSIEWLP for the duration of the
> >update.
>
> How is this propagated?
>
I've got several threads entangled here; don't let me confuse
you. We do the above for listing and object libraries; not
for ISPF profiles.
ENQ is ENQ. It gets propagated by GRS, or MIM, or whatever,
according to the rules the sysadmin establishes. The ENQ
is established by PARM, something like:
//STEP EXEC PGM=SERIAL,PARM='IEBGENER,SYSUT2/<parm-to-iebgener>'
... the PARM tells SERIAL what program to run and what DDNAMEs
to ENQUEUE the associated data set names of. Data following the
'/' is passed as PARM to the subject program.
The ENQ is transitory, for only the duration of the job step.
SERIAL waits for ENQ conflicts to be resolved.
Deadlocks are theoretically possible.
It's older than ISPF, which provides comparable facilities.
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
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
