Compile skeletons and panels

Code Pipeline interfaces to whichever compilers your shop uses. There are two ways to connect them:

• With Code Pipeline skels calling the standard compile procs.
• With Code Pipeline skels only.

Calling your procs

With Code Pipeline skels calling the standard compile procs:

• You will continue to use standard compile procs.
• Code Pipeline compile skels will invoke those procs.

The advantages are:

• The standard proc is still available to invoke outside of Code Pipeline.
• It may be more in keeping with your standards.

The disadvantages are:

• Both the proc and the skel must be updated if a new version of the proc is installed,
• There is a risk of forgetting to update the skel if the proc is changed, especially if they are supported by two different groups,
• It may be less obvious how it works and therefore how to fix it.

Using Code Pipeline skels

With Code Pipeline skels only:

• The separate compile procs would not be maintained.
• All of the compile JCL is within the skeleton.

The advantages are:

• It’s possible to define different skels for different steps of the compile, for example, the compile may be one skel, the link may be another, and the Db2 bind step may be in its own skel. The compile JCL itself may be built by file tailoring embedded skels together.
• The same argument applies as with JCL and PROCS, whether it makes more sense to have them together in one member or as two separate members.

The disadvantages are:

• The person who supports the Code Pipeline compile skels must either be the same person who supports the compilers or must work closely with that person to ensure that changes to the compile requirements are reflected in the proc,
• This may not fit well with your shop standards.