Insert of 64-bit Files
This process queries the F9860 table for all objects that have a file associated with them. The query uses the condition where the F9860->sigtffu1= 1 and not equal to "GT", "APP", "DSTR" and "88"(Not Applicable).
For each object that is retrieved from the F98780R, it will first check if the object has already been converted (through the ESU process or OMW) and if there is no include64 and source64 found, it will convert the include and source files into an include64 and source64. It will then insert all four files into the F98780R and F98780H along with the central object specs.
The objects that have files associated with them are business functions, tables, business views, and UBEs. All business functions and tables will have a file. Business functions that are NER (N*.c) and tables with TER(f*.c) have a file, but in 9.2.3.0, the files are not loaded into the repository. There is no need to store these in the repository because these are generated during the package build process and during the OMW process. If a business view has a .h file, the file is named B<view name>.h. If a UBE has a .h file, the file is named <ube name>.h. All these files are converted into an include64 and source64 directory.
The process produces these logs:
UBELog_64.log
BSFNLog_64.log
BSVWLog_64.log
TBLELog_64.log
NotCheckinLog_64.log
NotConvertLog_64.log
The first four logs list all objects that were selected from the F9860 table and processed.
For example:
Fri Mar 02 00:16:48 - 0 - BSFN Name B0100084 Fri Mar 02 00:16:52 - 1 - BSFN Name B0101500
where it is formatted:
<date> - <sequence> <object type> Name <name of object>.
The <sequence> is the sequence of when it was retrieved from the database.
The NotConvertLog_64.log lists all objects that were not converted. This could mean it found an include64 and source64 file so it did not have to convert them.
The NotCheckinLog_64.log lists all objects that were not checked into the path code.