About Source Code

A Source Code definition encapsulates the file containing the actual source code, so that the source code is stored under version control, in compliance with industry regulations. (See Versions of Component Objects.)

Every Oracle LSH Program must contain one primary source code object and may contain any number of additional (secondary) source code objects serving as subroutines.

Primary Source Code: Each Program contains one primary Source Code definition, listed first and given an Order number of one (1). When you execute the Program, the system launches the Source Code definition you have defined as Primary. Normally you write the primary source code especially for a particular Program. The primary Source Code definition contains the file the system executes when the Program is submitted. The primary source code references Table Descriptors, Parameters, Planned Outputs, and other Source Code instances defined in the Program by their Oracle or SAS name, as appropriate for the technology type. (See Writing Primary Source Code in PL/SQL and SAS Program and Source Code Types.)

Secondary Source Code: Secondary Source Code objects are those with any order number other than one (1). They are SAS macros or formats or PL/SQL packages that are, in most cases, called by the primary source code.

Source Code definitions have a Sharable attribute that, if set to Yes, makes them available for use as a definition source for Source Code instances in other Programs. You can create Program definitions especially for the purpose of storing sharable Source Code definitions. If you are working in SAS, you must create a Program definition of type Macro Catalog to store macros, or a Program definition of type Format Catalog to store formats. If you are working in Oracle technologies (Oracle Reports or PL/SQL) you can create a Program definition of type PL/SQL to hold sharable PL/SQL packages.

You can also create secondary Source Code especially for a particular program. In this case Oracle Life Sciences Data Hub stores both the Source Code instance and its definition in the Program in which you create them.

See Upgrading Source Code And Undoing Source Code Upgrades for information on how to upgrade Source Code instances pointing to a sharable Source Code definition.

For further information, see:

• Creating a SAS Macro Catalog
• Creating a SAS Format Catalog
• Creating a PL/SQL Package Storage Program

• Execution
  When you submit an Execution Setup to run a Program, the system performs tasks in the sequence listed in the following procedure.