MVSFORUMS.com

[JOSHI.SHOBHA]

Hi All,

I have a scenario like we had 6 digits Policy No. and now we are expanding it to 7 digit.
Policy no was a primary Key for the VSAM KSDS file where we have our data. Now I have been asked to increment the Key length without using any intermediate file or infact any other file. I have to do it with the same VSAM file. Is it doable ? As I doubt if it can be done as in VSAM KSDS I dont think that we can alter with the key

Please advise
Thanks
Shobha
_________________
Thanks

[kolusu]

[JOSHI.SHOBHA]

Thanks a lot !!!
_________________
Thanks

[dbzTHEdinosauer]

might have to modify the seq file (expand policy number by 1 byte) before repro back to new vsam file.

suggest you increase policy number to 10 or 12.

also, since the policy number field is being expanded by 1 byte, that means the record is also 1 byte longer. you are talking about modifying every module that accesses these records in order to reflect the new record length (as well as the new relative location of every field following policy number.

too bad the people who give you your instructions have so little understanding of computers.
_________________
Dick Brenholtz
American living in Varel, Germany

[JOSHI.SHOBHA]

Thanks a lot !!! Will suggest them this approach.

Thanks
Shobha
_________________
Thanks

[slade]

It may be more than "expanding the key". You may have to restructure the key data.

Do you want existing policy# A12345 to be changed to A123450 or A12345b or A012345? Some pgms may do math on the numeric part of the P#, e.g. add 1 to the high# to assign the next #.

Be careful.
_________________
Regards, Jack.

"A problem well stated is a problem half solved" -- Charles F. Kettering

[chandra]

Hi Dick and Jack,

We are having same situation. We are expanding the policy number from X(6) to X(10).

I am doing an analysis of building a tool that can change all the COBOL copybooks that are impacted, Programs that are have a working storage variables, BMS Maps, LRECL of all output files, Reports and the downstream impact of the LRECL change in the dataset finally the other systems that are interface with this system.

I am planning to write a REXX program that will change the all impacted copybooks from X(6) to X(10) after changing it will compare with the original copybook and list the difference for our reference.

Can you please let me know if you have any suggestions?
_________________
Regards,
Chandra

[papadi]

Suggest you have not yet discovered the size of the bear you plan to eat. . .

Identifying "every" point of impact is probably out of reach.
A couple of examples:
1. Nested copybooks
2. Generated "stuff" like Easytrieve code, sort control statements, other control statements.

If this is worked on, plan on this taking more than just a little bit of time/effort.

Is your management willing to do without your services while this is worked on?

Also, if this is worked on, i'd suggest scoping out pieces and implement these rather than trying to to this as one big exec.

Good luck
_________________
All the best,

di

[misi01]

You mentioned BMS maps. What about the scenario where a BMS layout has the policy number on a line and the rest of the line is "occupied" with other fields as well.

That could mean you'll have to do a redesign of the layout to accommodate those extra 4 bytes
_________________
Michael

[chandra]

Yes Misi01...That's true. We are analysing all the screens.

Thanks for pointing out...
_________________
Regards,
Chandra