Re: Dummy question on ISPF command

[Wayne Bickerdike]

or use SCLM to manage your files. Never met more than a handful of sysprogs
who wanted "controls"

On Tue, Dec 6, 2016 at 11:27 PM, Richards, Robert B. <
robert.richa...@opm.gov> wrote:

> > I would still prefer a seamlessly sequential approach where ISPF itself
> would roll over 01/99 to 02/00.
>
> I would not hold my breath for that enhancement. 
>
> Here's a simple thought: Assign each sysprog a version number. Document
> that assignment in ##VER member. VER is a sortable field. Issue SORT VER
> and at a glance, you know who is currently responsible for updating
> member(s). Yes, SORT ID accomplishes the same thing, I suppose (well, I
> told you it was a simple thought!).
>
> Bob
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jesse 1 Robinson
> Sent: Monday, December 05, 2016 6:43 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Dummy question on ISPF command
>
> I did not know about the VER or LEV command. I can see how they could be
> useful if employed rigorously according to some protocol. We are not a huge
> shop, but there are multiple people who are allowed/encouraged to manage
> their own pieces of the bigger pie. I would still prefer a seamlessly
> sequential approach where ISPF itself would roll over 01/99 to 02/00.
>
> .
> .
> 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
> robin...@sce.com
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Richards, Robert B.
> Sent: Monday, December 05, 2016 2:57 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: (External):Re: Dummy question on ISPF command
>
> I have gotten into the habit of using VER and LEV commands from within an
> edit session. I use "VER n" sparingly, but "LEV 0" quite a bit. When I see
> a non-zero level and I know I didn't change it, I cancel back out and see
> who the last changer was before I proceed with my update. Nothing that I
> ever edit reaches 99 unless I have never been into the member and those
> that I find I issue a LEV 0 against. :-)
>
> Bob
>
> -Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jesse 1 Robinson
> Sent: Friday, December 02, 2016 12:59 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Dummy question on ISPF command
>
> 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
> robin...@sce.com
>
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Tom Marchant
&g

Re: Dummy question on ISPF command

[Richards, Robert B.]

> I would still prefer a seamlessly sequential approach where ISPF itself would 
> roll over 01/99 to 02/00. 

I would not hold my breath for that enhancement. 

Here's a simple thought: Assign each sysprog a version number. Document that 
assignment in ##VER member. VER is a sortable field. Issue SORT VER and at a 
glance, you know who is currently responsible for updating member(s). Yes, SORT 
ID accomplishes the same thing, I suppose (well, I told you it was a simple 
thought!).

Bob 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Monday, December 05, 2016 6:43 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dummy question on ISPF command

I did not know about the VER or LEV command. I can see how they could be useful 
if employed rigorously according to some protocol. We are not a huge shop, but 
there are multiple people who are allowed/encouraged to manage their own pieces 
of the bigger pie. I would still prefer a seamlessly sequential approach where 
ISPF itself would roll over 01/99 to 02/00. 

.
.
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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: Monday, December 05, 2016 2:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Dummy question on ISPF command

I have gotten into the habit of using VER and LEV commands from within an edit 
session. I use "VER n" sparingly, but "LEV 0" quite a bit. When I see a 
non-zero level and I know I didn't change it, I cancel back out and see who the 
last changer was before I proceed with my update. Nothing that I ever edit 
reaches 99 unless I have never been into the member and those that I find I 
issue a LEV 0 against. :-)

Bob 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Friday, December 02, 2016 12:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dummy question on ISPF command

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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Friday, December 02, 2016 6:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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 chan

Re: Dummy question on ISPF command

[Jesse 1 Robinson]

I did not know about the VER or LEV command. I can see how they could be useful 
if employed rigorously according to some protocol. We are not a huge shop, but 
there are multiple people who are allowed/encouraged to manage their own pieces 
of the bigger pie. I would still prefer a seamlessly sequential approach where 
ISPF itself would roll over 01/99 to 02/00. 

.
.
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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Richards, Robert B.
Sent: Monday, December 05, 2016 2:57 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Dummy question on ISPF command

I have gotten into the habit of using VER and LEV commands from within an edit 
session. I use "VER n" sparingly, but "LEV 0" quite a bit. When I see a 
non-zero level and I know I didn't change it, I cancel back out and see who the 
last changer was before I proceed with my update. Nothing that I ever edit 
reaches 99 unless I have never been into the member and those that I find I 
issue a LEV 0 against. :-)

Bob 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Friday, December 02, 2016 12:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dummy question on ISPF command

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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Friday, December 02, 2016 6:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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 su

Re: Dummy question on ISPF command

[Richards, Robert B.]

I have gotten into the habit of using VER and LEV commands from within an edit 
session. I use "VER n" sparingly, but "LEV 0" quite a bit. When I see a 
non-zero level and I know I didn't change it, I cancel back out and see who the 
last changer was before I proceed with my update. Nothing that I ever edit 
reaches 99 unless I have never been into the member and those that I find I 
issue a LEV 0 against. :-)

Bob 

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Jesse 1 Robinson
Sent: Friday, December 02, 2016 12:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Dummy question on ISPF command

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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Friday, December 02, 2016 6:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dummy question on ISPF command

[CM Poncelet]

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
> robin...@sce.com
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On 
> Behalf Of Tom Marchant
> Sent: Friday, December 02, 2016 6:51 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
> 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dummy question on ISPF command

[Jesse 1 Robinson]

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
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Tom Marchant
Sent: Friday, December 02, 2016 6:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: Dummy question on ISPF command

[Tom Marchant]

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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: Dummy question on ISPF command

[Dyck, Lionel B. (TRA)]

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.

Hope this helps

--
Lionel B. Dyck (TRA Contractor)
Mainframe Systems Programmer 
Enterprise Infrastructure Support (Station 200) (005OP6.3.10)
VA OI Service Delivery & Engineering

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Rupert Reynolds
Sent: Friday, December 02, 2016 8:06 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXTERNAL] Re: Dummy question on ISPF command

And in an edit macro, you can (well, you could a few years ago) access the 
counts of changes and errors using

Address 'ISREDIT' (ChgC, ErrC) = CHANGE_COUNTS

and I assume there is an ISPF variable  already set for display in the long 
message from .
On 2 Dec 2016 05:26, "Chris Hoelscher" <choelsc...@humana.com> wrote:

> At least at our shop, pressing F1 AFTER the change will prvide a count 
> at the bottom of the screen
>
> Chris Hoelscher
> Technology Architect, Database Infrastructure Services Technology 
> Solution Services
> : humana.com
> 123 East Main Street
> Louisville, KY 40202
> Humana.com
> (502) 714-8615, (502) 476-2538
>
> > -Original Message-
> > From: IBM Mainframe Discussion List 
> > [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Peter
> > Sent: Friday, December 02, 2016 12:20 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: [IBM-MAIN] Dummy question on ISPF command
> >
> > Hi
> >
> > Apologies for asking a dummy question
> >
> > When we do C ALL DATA1 DATA2 in a PS or PDS. Is it possible to get a
> count of
> > changes it made ?
> >
> > Since I am not able to see the changes at the top right corner.
> >
> > Peter
> >
> > 
> > -- For IBM-MAIN subscribe / signoff / archive access instructions, 
> > send
> email to
> > lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> The information transmitted is intended only for the person or entity 
> to which it is addressed and may contain CONFIDENTIAL material.  If 
> you receive this material/information in error, please contact the 
> sender and delete or destroy the material/information.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send 
> email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dummy question on ISPF command

[Rupert Reynolds]

And in an edit macro, you can (well, you could a few years ago) access the
counts of changes and errors using

Address 'ISREDIT' (ChgC, ErrC) = CHANGE_COUNTS

and I assume there is an ISPF variable  already set for display in the long
message from .
On 2 Dec 2016 05:26, "Chris Hoelscher"  wrote:

> At least at our shop, pressing F1 AFTER the change will prvide a count at
> the bottom of the screen
>
> Chris Hoelscher
> Technology Architect, Database Infrastructure Services
> Technology Solution Services
> : humana.com
> 123 East Main Street
> Louisville, KY 40202
> Humana.com
> (502) 714-8615, (502) 476-2538
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> > On Behalf Of Peter
> > Sent: Friday, December 02, 2016 12:20 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > Subject: [IBM-MAIN] Dummy question on ISPF command
> >
> > Hi
> >
> > Apologies for asking a dummy question
> >
> > When we do C ALL DATA1 DATA2 in a PS or PDS. Is it possible to get a
> count of
> > changes it made ?
> >
> > Since I am not able to see the changes at the top right corner.
> >
> > Peter
> >
> > --
> > For IBM-MAIN subscribe / signoff / archive access instructions, send
> email to
> > lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
> The information transmitted is intended only for the person or entity to
> which it is addressed
> and may contain CONFIDENTIAL material.  If you receive this
> material/information in error,
> please contact the sender and delete or destroy the material/information.
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dummy question on ISPF command

[Mike Schwab]

Press F1 for a longer message.

On Thu, Dec 1, 2016 at 11:20 PM, Peter  wrote:
> Hi
>
> Apologies for asking a dummy question
>
> When we do C ALL DATA1 DATA2 in a PS or PDS. Is it possible to get a count
> of changes it made ?
>
> Since I am not able to see the changes at the top right corner.
>
> Peter
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Dummy question on ISPF command

[Chris Hoelscher]

At least at our shop, pressing F1 AFTER the change will prvide a count at the 
bottom of the screen

Chris Hoelscher
Technology Architect, Database Infrastructure Services
Technology Solution Services
: humana.com
123 East Main Street
Louisville, KY 40202
Humana.com
(502) 714-8615, (502) 476-2538

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
> On Behalf Of Peter
> Sent: Friday, December 02, 2016 12:20 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [IBM-MAIN] Dummy question on ISPF command
> 
> Hi
> 
> Apologies for asking a dummy question
> 
> When we do C ALL DATA1 DATA2 in a PS or PDS. Is it possible to get a count of
> changes it made ?
> 
> Since I am not able to see the changes at the top right corner.
> 
> Peter
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

The information transmitted is intended only for the person or entity to which 
it is addressed
and may contain CONFIDENTIAL material.  If you receive this 
material/information in error,
please contact the sender and delete or destroy the material/information.


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN