When exporting COBOL members from Panvalet to a PDS(E) library with ++WRITE, the including COBOL sequence numbers are provided through the $2SF078 exit.
But if a ++INCLUDE statement is expanded, the sequence numbers of the included member are inserted into the exported member. Thus disturbing the COBOL number sequencing.
If the exported member in the PDS(E) library is edited with the ISPF editor afterwards, the ISPF editor issues a warning that no appropriate COBOL numbers exist and changes the profile.
Is there a way to export a member with expanded ++INCLUDEs with ascending COBOL sequence numbers or is there a way to prevent the ISPF editor from automatically change the ISPF profile settings from NUMBER ON COB to NUMBER OFF in these cases?
With Panvalet, there is no chance to export a member with expanded ++INCLUDEs with renumbering the sequence numbers of the complete exported COBOL source.
Also, there is no way to prevent the ISPF editor from automatically changing the profile settings from NUMBER ON COB to NUMBER OFF.
Currently, the edited COBOL member on PDS(E) doesn't have ascending sequence numbers in these case. So you have to go to the ISPF edit command line the first time, issue NUM ON COB and save the member. The member will automatically be renumbered. Next time the member is edited, ISPF will PICK up the COBOL settings from the profile.
Alternatively, it may be checked whether this can be done by a (site written) ISPF EDIT macro.