(SYSLIB) Programming Reference Manual - Public Support Login ...

BSP$-Program File Basic Service Package
In this example, BSP$ adds an element to a program file. The following two buffers and
one packet are required:
• FCT is for the file control table
• ELTTBL is for the program file element table
• ADDPKT is for a packet that holds information about the element to be added
The first call to BSP$ reads the file control table. The file control table must be read
before any other calls are made to BSP$.
The next call to BSP$ is to read the program file element table. This table must be read
before elements are added, deleted or searched for.
The BSP$ call to ETIA$ adds the element described in the add packet ADDPKT to the
contents in the file TESTFILE. The element name is NEWPROGRAM with version name
VERS-3. It is a symbolic element, cycle 0, with a maximum cycle limit of 5.
ELTLEN is the sector length of the element. ELTADDR is the starting sector address of
the element in the file TESTFILE. The calling program must write the actual text of the
element to the file using the SDFO routine.
When the element is added to the program file element table, the table must be written
back to WPFET$. The next write location is updated by adding the element sector
length to word 7 of the FCT. A call to WFTI$ writes the updated FTI back to the file.
This completes updating of the file.
5.3. LEPF Considerations
This section contains additional information, limitations, restrictions, and considerations
pertaining to LEPFs and their use.
The following are general limitations and restrictions:
• LEPFs are first supported by the BSP$ contained in SYSLIB level 76R1. LEPFs are
not recognized as program files by any prior SYSLIB level.
• The initial implementation of LEPFs is intended primarily for use by MAPPER, as a
container for large MAPPER reports (symbolic elements) that have over 262,143
sectors of element text.
• Initially, only MAPPER, FURPUR, PCFP, and BSP$ support LEPFs.
• Initially, LEPFs are not supported by the Exec, including the ER PFx$ interface and
the command line interface (@ADD, @START, @XQT, and so on).
• Initially, LEPFs cannot contain procedure elements (element type 1, subtype 035,
and element types 2, 3, and 4), relocatable elements (element type 5), and
executable elements (element type 6).
• Calling programs that are not modified will not recognize LEPFs as program files.
This includes programs that call the relocatable version of BSP$, even when they are
re-collected with SYSLIB level 76R1 or higher.
7833 1733–004 5–35