Interesting, by the way, this is C code compiled with z/OS XL/C, so I have no control over the structure of the module.
Does this mean that such code can't be managed by AMASPAZP? I know I can DUMPT ALL the CSECTS, but what about zapping the content? Thanks, mario On Sat, 12 Feb 2022 12:51:40 -0800, Michael Stein <[email protected]> wrote: >> The utility fails with RC 8 complaining that CSECT PRIV000010 doesn't exist. > >It doesn't. Private code is "PC" not a csect. > >The assembler can produce it if you don't start with a CSECT statement. > >From an old MVT manual: > > GC26-3813-3_OS_VS_Linkage_Editor_and_Loader_May75.pdf > > Private code -- an unnamed control section. The external symbol > dictionary entry specifies the length of the control section, and > the origin. The name field contains blanks. > >---------------------------------------------------------------------- >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
