IEBUPDTE will update PDS members without changing their VVMM stats in cols 73-80, if that helps.
On 02/12/2016 17:58, Jesse 1 Robinson wrote: > I'm a huge fan of both ISPF Stats and the Version/Mod values stored in PDS > members columns 73 - 80. Preserving them requires a bit of forethought. When > updating a member, it's common practice to create a new or backup member. > Unfortunately, the 'simplest' ways are the worst: > > 1. Bad e.g. Edit a new (empty) member, copy all lines from the production > version into the empty guy, then save the new version. This technique loses > all previous V/M numbers because ISPF starts over for the new member. > > 2. Bad e.g. Edit the current member directly and before making any changes, > copy all lines to Create the backup member. This preserves the current V/M > numbers but mangles the backup member. > > In order to preserve both Stats and V/M line numbers, you need to take the > out-of-line step of copying the current member to either a backup or future > name *outside of edit*. You can use Option 3.3 or some other process like > StarTool Copy. This is a little more hassle, but the goal is to have > backup/future member look exactly like the production member in every way > except name. When you edit in updates, ISPF will adjust V/M numbers from the > current level forward. Nothing lost. > > Some gotchas. > > -- Deleted lines disappear without a trace. You have to infer lines missing > from one iteration to the next. I.e. no logging. > > -- ISPF supports Mod numbers from 00 - 99. There is no rollover, and the > Version number is never incremented. This is a problem for a long-lived PDS > like PARMLIB, which may last for years/decades. Eventually the Version > reaches 99 and stays there despite subsequent edits. You can no longer > compare versions by line number. > > -- Remember that there are no ISPF stats for a PS dataset. Consider this fact > when deciding what kind of file you want to maintain. > > . > . > J.O.Skip Robinson > Southern California Edison Company > Electric Dragon Team Paddler > SHARE MVS Program Co-Manager > 323-715-0595 Mobile > 626-302-7535 Office > [email protected] > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Tom Marchant > Sent: Friday, December 02, 2016 6:51 AM > To: [email protected] > Subject: (External):Re: [EXTERNAL] Re: Dummy question on ISPF command > > On Fri, 2 Dec 2016 08:20:41 -0600, Dyck, Lionel B. wrote: > >> In the normal ISPF Edit (option 2) member list if you use PF10 or PF11 >> to shift left or right) you will see a display with Size, Init, and Mod >> columns. These display, respectively, the current size of the member, >> the initial size of the member, and the number of records changed. >> To get an accurate (non-0) Mod count you must have numbers enabled in >> the member. > > In the line number columns 79-80, ISPF Edit stores the Mod number of the > change that last modified the line. The " VV MM" column shows the latest Mod > number that was used to edit the member. Renumber does not change columns > 79-80, but only the actual line number in 73-78. Unnumber, of course removes > them and the information is lost. > > The mod count is the count of all lines that contain a value that is not > "00". If you want to know how many likes were changed by the last edit > session, you can use F ALL "nn" 79, where nn is the value shown in the MM > column in the directory listing. > > And none of this is answers the OP's original question, but others have > provided answers. > > -- > Tom Marchant > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
