Thanks for your replies. Clearer now.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
The binder's continuing support for SETSSI and the system status index
is entirely appropriate: historically, they have been used for many
purposes.
The availability of control-section specific IDRs and the IDENTIFY
binder control statement have, however, made SETSSI obsolescent.
SETSSI sets the
[QUOTE]system status index (SSI): A field in the directory entry of a program
module which can be used to record current maintenance status. [/QUOTE]
I know of a Change Management Tool storing an identifier which is unique for a
specific build of a module in the SSI field. By using the SSI, an
In 7215641216907067.wa.supportdunnitsys@listserv.ua.edu, on
11/27/2014
at 07:34 AM, Support, DUNNIT SYSTEMS LTD. supp...@dunnitsys.com
said:
I read the manual. Why is this used?
Audit trail.
Why is this used? What are the pitfalls of relinking a load module
and dropping this value?
The
I read the manual. Why is this used? What are the pitfalls of relinking a load
module and dropping this value?
TIA!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with
