Information Systems:Compiling ASW Programs and Objects

(Note that the following is how I understand ASW to work; but it may not be correct.)

ASW uses shared access paths. When you run a job, all the files used by any of the programs that can possibly be called are pre-opened in either input or update mode. The cross reference is read to determine which files to open, and in what mode.

In PDM, option AC (for ‘ASW Compile’) will compile the object, and add it to this cross reference.

If you add a custom program, which is the only program that updates a particular file, to an existing flow, it will bomb. As no associated program in the cross reference updates the file, it will be pre-opened in input only mode. There are two ways of fixing this. The only way a custom program could have been added is to have called it from an ASW program. Add the file in update mode to that program, and compile it with AC. That will update the cross reference, and change the pre-open mode of that file from input to update. Or compile the custom program itself with AC.

If you are changing an existing custom program, the way of telling which compile to use, is to see if the program is already in the cross reference. If it is, use AC; if not, use 14.

Go  crossref
Select option 2. Enquire on program structure
Key the program name into ‘Pgm’ and press enter

If nothing comes up, and the program does use files, it is not in the cross reference.