W dniu 2016-03-03 o 04:55, Anthony Thompson pisze:
I'm supposing that when you say HCD you mean IODF.
Further, when you mention REXX code, I'm guessing you are referring to Mark
Zelden's IPLINFO REXX.
This interrogates a couple of control blocks that I can't see documented, not
in the Data Areas manuals, nor in MACLIB/MODGEN (IOVT and CDA ).
I'd try to verify your assertion that these control blocks aren't updated by an
ACTIVATE, but my company is in the throes of a mainframe upgrade and the
sandbox sysplex is currently unavailable.
If your REXX runs under a userid with the authority to issue system commands,
I'm wondering if you can trap the output from a 'D IOS,CONFIG' command and
analyse the results from that.
Mr. Zelden may have more to say..
1. HCD vs IODF. Actually both names are not 100% accurate. There is no
*simple* and accurate name, it is I/O configuration. HCD is an
application to create such configuration, IODF is dataset which contains
the configuration, but there is also IOCDS, and active configuration in
MVS (let's focus on this OS) and HSA.
2. D IOS,CONFIG shows current configuration (IODF name) for both HSA and
MVS, but it doesn't show whether the config was activated after IPL.
Even case where IODF HSA <> IODF MVS does not mean there was an
activate, because system could be IPLed with non-matching IODF (which in
turn disallow dynamic changes).
3. AFAIK Mark's IPLINFO (great tool BTW, thank you Mark!) does not show
whether dynamic change took place.
BTW: What's the goal? IMHO there are some other methods to get such
information. Not to mention dynamic activate should be strictly
controlled and performed only by persons who really know what they do.
Regards
--
Radoslaw Skorupka
Lodz, Poland
--
Treść tej wiadomości może zawierać informacje prawnie chronione Banku
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.
This e-mail may contain legally privileged information of the Bank and is
intended solely for business use of the addressee. This e-mail may only be
received by the addressee and may not be disclosed to any third parties. If you
are not the intended addressee of this e-mail or the employee authorized to
forward it to the addressee, be advised that any dissemination, copying,
distribution or any other similar activity is legally prohibited and may be
punishable. If you received this e-mail by mistake please advise the sender
immediately by using the reply facility in your e-mail software and delete
permanently this e-mail including any copies of it either printed or saved to
hard drive.
mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa,
www.mBank.pl, e-mail: [email protected]
Sąd Rejonowy dla m. st. Warszawy XII Wydział Gospodarczy Krajowego Rejestru
Sądowego, nr rejestru przedsiębiorców KRS 0000025237, NIP: 526-021-50-88.
Według stanu na dzień 01.01.2016 r. kapitał zakładowy mBanku S.A. (w całości
wpłacony) wynosi 168.955.696 złotych.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
