Re: Is 00000000 a valid sequence number?
On Mon, 3 Mar 2008 10:01:25 -0600, Paul Gilmartin [EMAIL PROTECTED] wrote: But if I intend to write a sequence number validator, I'm concerned less with what the producers generate than with what the consumers (IEBUPDTE, ISPF, ISRSUPC, other?) accept. ISPF is both a generator and a consumer. In ISPF EDIT, with NUM ON STD, if you try to change a sequence number to 0, you get 'Some input data ignored'. Turn NUM OFF and you can change the data to 0, then turn NUM ON STD and EDIT is still okay with it. I then turned NUM ON COB, could not change the number, NUM OFF, changed it, and turned NUM ON COB and EDIT was still happy with it. IEBUPDTE happily added a member with sequence number 0. Edit turned NUM ON and it happily showed sequence 0. Other programs' results may vary. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Is 00000000 a valid sequence number?
On 2 Mar 2008 17:43:56 -0800, [EMAIL PROTECTED] (Shmuel Metz , Seymour J.) wrote: As far as the ISPF editor, the default is initial value 100 w/ increment 100; That's what you get when you use ISPF to create a member, but ISPF can also work with members created externally. Also, ISPF will allow you to copy or move a line to the beginning of the member. Or internally when you add lines anywhere within a member and don't renumber. (and autonum is off) Help shows: When edit is assigning a number to a record, it attempts to pick a number that is between the numbers on either side. If possible a multiple of 100 is selected. If this is not possible a multiple of 10 is selected. And if that is not possible, the next sequential number is selected. Examples:between 200 - 400 insert 300 (next multiple of 100) between 300 - 400 insert 310 (next multiple of 10)between 310 - 400 insert 320 (next multiple of 10)between 310 - 320 insert 311 (next ascending number)between 310 - 311 insert 311 (and renumber the original 311 to 312) In the last example, an existing record had to be renumbered to maintain an ascending sequence. Edit will automatically renumber as many records as necessary to maintain ascending sequence numbers, but it will not renumber any records that do not require renumbering. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Is 00000000 a valid sequence number?
On Sun, 2 Mar 2008 18:01:56 -0500, Shmuel Metz (Seymour J.) wrote: In [EMAIL PROTECTED], on 02/29/2008 at 03:15 PM, Steve Comstock said: As far as the ISPF editor, the default is initial value 100 w/ increment 100; That's what you get when you use ISPF to create a member, but ISPF can also work with members created externally. Also, ISPF will allow you to copy or move a line to the beginning of the member. Thanks for the followups. But if I intend to write a sequence number validator, I'm concerned less with what the producers generate than with what the consumers (IEBUPDTE, ISPF, ISRSUPC, other?) accept. I want neither to report false negatives by passing values that some consumer utility might reject nor false positives by unnecessarily rejecting values that some unknown producer utility or even a manual retouch with an editor might generate. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Is 00000000 a valid sequence number?
In [EMAIL PROTECTED], on 02/29/2008 at 03:15 PM, Steve Comstock [EMAIL PROTECTED] said: As far as the ISPF editor, the default is initial value 100 w/ increment 100; That's what you get when you use ISPF to create a member, but ISPF can also work with members created externally. Also, ISPF will allow you to copy or move a line to the beginning of the member. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Is 00000000 a valid sequence number?
Much as I despise sequence numbers, I sometimes need not merely to tolerate, but to support them. Now, I want to check whether sequence numbers are valid, monotonically increasing, etc. So, knowing IBM's penchant for considering intuitive boundary conditions invalid, what's the mimimal valid sequence number, or 0001? Is there an off-the-shelf sequence number checker I can use. IEBUPDTE seems determined to give me a hard time when I try: //STEP EXEC PGM=IEBUPDTE //SYSIN DD DUMMY //SYSUT2DD DUMMY It won't work with empty SYSIN. OK, that's kinda reasonable, so I give it a REPRO command. Now it complains about SYSUT2 DD DUMMY. Why, dammit!? When I supply a temporary data set for SYSUT2, it reports no problem with invalid line numbers on SYSUT1. Is there any easy way to get IEBUPDTE (or any other utility) to report invalid line numbers and do little else? I'll try ISRSUPC with UPDMVS8 next. (I know it's trivial, but I always like to avoid RYO.) Continuing in this vein, SMP/E provides ++SRCUPD and ++MACUPD MCS. Is there any similar construct to apply source usermods to other data element types? If not, there's little motivation to provide valid sequence numbers on those types. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Is 00000000 a valid sequence number?
Paul [EMAIL PROTECTED] wrote: Much as I despise sequence numbers, I sometimes need not merely to tolerate, but to support them. Now, I want to check whether sequence numbers are valid, monotonically increasing, etc. So, knowing IBM's penchant for considering intuitive boundary conditions invalid, what's the mimimal valid sequence number, or 0001? As far as the ISPF editor, the default is initial value 100 w/ increment 100; as you insert lines, it will use smaller increments as necessary. I don't recall every seeing a way to change the initial and increment values. Is there an off-the-shelf sequence number checker I can use. IEBUPDTE seems determined to give me a hard time when I try: //STEP EXEC PGM=IEBUPDTE //SYSIN DD DUMMY //SYSUT2DD DUMMY It won't work with empty SYSIN. OK, that's kinda reasonable, so I give it a REPRO command. Now it complains about SYSUT2 DD DUMMY. Why, dammit!? My guess is that a DUMMY datast can't get its DCB parameters copied from SYSUT1; a tempory data set, on the other hand, is real enough to allow copying DCB parameters from SYSUT1 to SYSUT2. When I supply a temporary data set for SYSUT2, it reports no problem with invalid line numbers on SYSUT1. Is there any easy way to get IEBUPDTE (or any other utility) to report invalid line numbers and do little else? I'll try ISRSUPC with UPDMVS8 next. (I know it's trivial, but I always like to avoid RYO.) Continuing in this vein, SMP/E provides ++SRCUPD and ++MACUPD MCS. Is there any similar construct to apply source usermods to other data element types? If not, there's little motivation to provide valid sequence numbers on those types. I don't do SMP/E, since IANASP, to quote someone. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393-8716 http://www.trainersfriend.com z/OS Application development made easier * Our classes include + How things work + Programming examples with realistic applications + Starter / skeleton code + Complete working programs + Useful utilities and subroutines + Tips and techniques -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
