> We'd still like to know why loading the program from a PDSE > apparently changed how (and more importantly, where) the system > passed the PARM= string.
PDSEs are 4K page oriented, so when loaded, they are generally going to start at a 4K boundary. When loading from a PDS, fetch processing simply does a GETMAIN for the storage. If the size of the module is at least 2 pages, but not a page multiple, the Getmained storage (and thus the load module) will be aligned to end on a 4K boundary if D DIAG shows VSM USEZOSV1R9RULES(YES) or it will be aligned to start on a 4K boundary if you have VSM USEZOSV1R9RULES(NO) Your results suggest that you are using the default of VSM USEZOSV1R9RULES(YES). I would expect the location of the PARM= string to be the same, regardless of PDS vs. PDSE. However, I would expect that changing the setting for VSM USEZOSV1R9RULES will change the location of the PARM= string. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
