If you are going to use z/OS you
must learn some JCL. It really is not all that hard - though I must admit I've been using it for more than 40 years. My response to your initial post suggested you look at several possible cataloged procedures, which you can easily do with ISPF. Most compiler oriented cataloged procedure imply their purpose in the characters at the end of the procedure name.
- C - The procedure will compile a program
- L - The procedure will lin kedit a program
- G - The procedure will execute ("go")a program
So a procedure xxxCLG will compile, link edit, and execute a program. Something like xxxCG will compile, and in one step run a linking loader and execute a program.
A "linking loader," which is probably a strange concept to you, prepares executable code in storage without preparing a load module. The idea has been around for a long time in mainframes because the mainframe linkage editor was fairly slow, and the overhead to run a separate linkage editor step was very high. A few software vendors came up with the idea of a linking loader, and IBM produced its own, which kind of blew the vendor provided linking loaders out of the water. In the 1990s, when IBM replaced the 1960s derived linkage editor with the Binder, rather than continue with a linking loader as a separate program, as was done in the 1960s, the linking loader was included with the Binder, though it appears to be a separate program.
In most shops, the IBM procedures, along with many shop specific procedures are in a data set called 'SYS1.PROCLIB. Look there first.
Posted: Thu Dec 20, 2012 4:21 am