The following objects have files that need to be managed on a 64-bit system:
Business Function (BSFN: including C, NER, TER)
Batch Application (UBE)
Business View (BSVW)
The source64 and include64 directories are added locally and are in the same location as the source and include directories. The Deployment Server will not contain the source64 or include64 directories.
The repository table will be inserted/updated with a single record for each object; the record will contain a PAR file with source and include directories in 32-bit mode and in 64-bit mode, depending on how the release flag is set.The history table record will be inserted with the same PAR file.
The check-out process will:
Retrieve the object specs from Central Objects.
Retrieve the 32-bit and 64-bit source and include files from the repository table (F98780R); if there is not a record in the repository tables, go through the process of creating and inserting one. The Deployment Server only has the include and source files (32-bit files) so the 64-bit files will be generated during this process and put into the repository.
Extract the files to a temporary location.
Copy the temp files to the local source and include directories.
Note:This process is the same for Get and Restore from the save location. The Advanced Get process is similar, but will not create a record in the repository/history tables if the record does not exist there, in this case the files from the Deployment Server will be used.
A Get will update the repository/history if there is no record there, for example: A Get from the development pathcode (DV920), will update the F98780R/H tables in Central Objects - DV920.
A Restore from the Save pathcode will update the repository/history for the Save location, for example: A Restore from the INDEV920, will update the F98780R/H tables in Central Objects - INDEV920. A Restore from PAR file will note update the repository/history tables.
An Advanced Get from a chosen pathcode will not update the repository/history tables.
The check-n process will:
Run the conversion process over the files.
Update/Insert (new objects) the specs of the object in Central Objects.
Update/Insert the 32-bit files on the Deployment Server in the current source/include locations.
Copy the 32-bit and 64-bit files (along with the other necessary files to be zipped into the PAR file) to the temporary location.
Zip all files from the temporary location into a PAR file and update/insert the record to the repository and history tables (F98780R/H). The PAR file will contain the directories include, source, include64 and source64.
Note:This process if the same for Save to the save location.
The transfer process will:
Utilize the OMW Transfer Activity Rule to determine the source and target locations of the objects.
Transfer the spec information of the object to the target location.
Update/Insert the file on the Deployment Server to the target source/include locations.
The record in the source repository is copied (inserted or updated) to the target repository table and the target history table is inserted as well.
There is no conversion performed during transfer.
The delete process will:
From local: Remove the 32-bit and 64-bit files associated with the object from the local source and include directories.
From the server: Remove the 32-bit files associated with the object from the deployment server source and include directories. Remove the record of the object from the F98780R.
From save location: Remove the 32-bit files associated with the object from the Deployment Server source and include directories. Remove the record of the object from the F98780R table in the save location data source.
On Transfer: Remove the 32-bit files associated with the object from the Deployment Server source and include directories. Remove the record of the object from the F98780R table in the target location data source.
Note:The process of deleting the specs for the object has not changed, that process will remain as it is now.