Posted: Thu Dec 12, 2013 8:36 pm Post subject: IEHLIST - output fields unformated outpu
Code:
DIRECTORY INFO FOR SPECIFIED PDS ON VOL PR9TFB
FILE.NAME.LOOKING.AT
MEMBERS TTRC VARIABLE USER DATA ---(USER DATA AND TTRC ARE IN
$TEMPLNT 01740A0F 0107000301 02287F0104 310F101200 3900380000 C3D6E2
ACS5TXXX 010B070F 0103002500 95292F0095 293F143600 3200310000 C3D6E2
ACS5T005 010B090F 0102004300 95293F0095 293F112500 3200320000 C3D6E2
I have 2 snap shots of the same dataset at different times. I have figured out that if it is a PDS and compressed then the TTR will change, what about the variable user data, can I count on that changing? Even for example if I typed a charachter into a existing space? The TTR seems to stay constant with a PDSE..... Thanks for any feed back!
When you change something which affects any of that, the value will change. For instance, with your example of modifying one blank, the number of lines changed should be reflected in the user-data.
Note: Where the document refers to "packed decimal" it is not quite being straight with you. The format is actually Binary Coded Decimal. Looks like "packed decimal" but with no low-order sign half-byte.
Bear in mind that the ISPF statistics can just be cleared easily. What are you actually trying to do?
When you change something which affects any of that, the value will change. For instance, with your example of modifying one blank, the number of lines changed should be reflected in the user-data.
Note: Where the document refers to "packed decimal" it is not quite being straight with you. The format is actually Binary Coded Decimal. Looks like "packed decimal" but with no low-order sign half-byte.
Bear in mind that the ISPF statistics can just be cleared easily. What are you actually trying to do?
First off thanks for the responce
Audit control....snaps shots of the PDS, mathcing endevor back to packages, and none endevor keeping track of, other steps with be to tie it all together with documented changes.
What I think I am seeing is a compress is being automaticly preformed on the library and the PDS directory is changing, I could be wrong but thinking logicly it fits. Yes I will have storage convert these to libraries, but I do know of one library which can't because a COBOL program from the 80's reads it and I had to have them convert it back.
In the instance of a space , the number of lines will change? Am I looking at this as 80 byte records but when the file is actualy stored it is different? Load modules fit what your saying, but non loads slighty different.
Stats are off on all libraries, a good portion of them are controlled by endevor but with our processes some could setup a production job to copy and bypass endevor alltogether......or as I have seen once before someone moving a proc higher up into the search order, support did this once and overrode a producton proc, later on when issues were encountered a lot of issues occured due to looking at the wrong code, and of course if endevor controlled extracting from endevor you will get it without changes made outside of endevor...
Joined: 03 Jan 2003 Posts: 1014 Topics: 13 Location: Atlantis
Posted: Fri Dec 13, 2013 3:12 pm Post subject:
I would not rely on user data for *anything*.
They are easily changed by copies, ISPF utilities and services, utilities, macros and anything else that writes to the PDS. They are sort of 'defacto' owned by ISPF with an ISPF defined format, but that format is implemented by many products and library systems, sometimes incorrectly or, to be nice, differently.
TTRs could be fooled by opening an output DCB for "update in place" for a PDS (not a PDSE I guess). Or doing a compress-change-compress if the member is at the end of the PDS.
For audit, the only way to do this in my opinion is to read the contents of the members, generate an md5sum, SHA hash or something like that store it externally. Take that with a grain of salt... I never worked in a shop that formally audited source code for changes. But I did work on the ISPF code that implemented the statistics a few decades ago and even changed the format once myself (I forget why. I think I added a bit somewhere). _________________ New members are encouraged to read the How To Ask Questions The Smart Way FAQ at http://www.catb.org/~esr/faqs/smart-questions.html.
15-16
Current number of lines, in hexadecimal format
17-18
Initial number of lines, in hexadecimal format
19-20
Number of modified lines, in hexadecimal format
If you change one blank on a line to something else, the "Number of modified lines" will change.
The problem for the purpose of audit is as outlined by semigeezer. They are "notes" rather than something which has "data integrity". They reflect what the ISPF editor has done to a member, since the last time that something else did something to it and until the next time something else does something to it.
I'm not sure why you have a mix of stuff inside Endevor and outside of Endevor and which is "auditable". Wouldn't ensuring that everything that is "Production" is in Endevor solve your problems with PDSs?
Endevor does control its libraires, but people have been known to setup copy jobs via tempory production jobs, thus bypassing endevor. This for the most part will placate the auditors and show we are minotoring it. Taking these changes, matching to endevor packages, and onto a feed from service now will go a long way towards the retoric. Over the next year we have to pull apart RACF, it really is a mess!
What I did notice with IEHLIST is if the library is a load module the TTR always changes, but when a non loadlib is looked at the user data changes and the TTR is not touched, unless it is compresed of course.
I understand someone could open the PDS in a job, this is more of a monitoring exercise than anything.
For now I am past the IEHLIST (but down the road I can replace), I have a proc which runs against any PDS/PDS, generates the IEHLIST into a GDG by dataset name. Reads those GDGs into Superc and produced of file read into a SAS job writing out a file with the library name, the member name, the type of change(add modify delete). Next is to get listing out of endevor...this will be a challenge.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum