Adding a File to a Rapid Fire Job

Adding one or more files to a Rapid Fire job is easy when you follow these steps:

Add File
Add Area
Add Conversion
Add Command

Add File

Expand a Job node and select New -> File... from the context menu of the Files node. Then enter the following attributes:

Position - The position number of the file. The objects of the shadow environment are compiled in the sequence of the position numbers.

File - Enter the name of the file that is copied. The names of the production and shadow libraries are found by evaluating the associated Area entry.

Type - Enter the type of the file: *PHYSICAL or *LOGICAL. You should also add logical files to your Rapid Fire job, in case you want Rapid Fire to create the required logical files when creating the shadow environment.
It is recommended to create the logical files before the copy process starts, because creating the logical files after the physical file has been updated can take significant time, depending on the number of records in the physical file.

Copy program - Enter the name of the program that you want to use for copying the records or select *GEN to let Rapid Fire generate a copy program for you. For logical files only *NONE is allowed.

Copy program library - Enter the name of the library where the copy program is stored.
Rapid Fire stores a generated copy program in the shadow library.

Conversion program - Enter the name of the conversion that you want to use for converting records or select *NONE.

Conversion program library - Enter the name of the library where the conversion program is stored.

Add Area

Expand the created File node and select New -> Area... from the context menu of the Areas node. Then enter the following attributes:

Area - Enter the name of the area. The name must follow the rules for host object names.

Library - Enter the name of a production library that you added to the Rapid Fire job beforehand.

Library list - Enter the name of the library list that you want to use for compiling the objects of the shadow environment.

Library CCSID - Enter the CCSID of the files of the production library. Rapid Fire executes the copy job with that CCSID to properly create the shadow environment. The CCSID is also assigned to the copy job while copying data.

Command extension - Add additional parameters that are added to the compile command that is used for compiling the file in the shadow environment. For example, if the base command was CRTPF, then parameter SRTSEQ could be different for each area.

Add Conversion

Expand the created File node and select New -> Conversion... from the context menu of the Conversions node. Then enter the following attributes:

Field to convert - Enter the name of the field the conversion rules apply to.

Rename field in old file to - Enter a new name if you need to rename a field in the old file, because you need to access the old value in a conversion statement. It is up to you, to fill a renamed field in the target record format.
Select *NONE if renaming is not required.

Conversions - Enter one or more conversion statements for example if you need to convert a numeric field to a date field. Each statement must be a valid RPG statement.

Sample copy programs

Generated copy program where the record format IDs of the old and new file did not change. Simple conversion statement that assigns a fix value to the existing field X1ERR. The field names of the source and target file are the same.

Generated copy program where the record format IDs of the old and new file did not change. IF/ELSE conversion statements converting field X1ERR from alpha-numeric to numeric. The field names of the source and target file are the same.

Generated copy program where the new record format has the new field X1NEWCOL. Simple conversion statement that assigns a fix value to the existing field X1ERR. The field names of the source and target file are prefixed with S_ and T_ since the record format has changed.

Add Command

Expand the created File node and select New -> Command... from the context menu of the Commands node. Then enter the following attributes:

Command type - Enter the type of the command. The available command types and their meanings are:

*PRERUN : Command that is executed before the compile command.

*COMPILE : Command that is used for compiling the object.

*POSTRUN : Command that is executed after the compile command.

Sequence - Enter a sequence number. Commands of the same type are executed in the ascending order of their sequence numbers.

Command - Enter the CL command that you want to execute. The following replacement variables are available:

&LIB : Variable that is replaced with the name of the library where the object will be stored.

&FILE : Variable that is replaced with the name of the object that is compiled.

Make sure to specify the replacement variables in upper case.

Position	-	The position number of the file. The objects of the shadow environment are compiled in the sequence of the position numbers.
File	-	Enter the name of the file that is copied. The names of the production and shadow libraries are found by evaluating the associated Area entry.
Type	-	Enter the type of the file: PHYSICAL or LOGICAL. You should also add logical files to your Rapid Fire job, in case you want Rapid Fire to create the required logical files when creating the shadow environment. It is recommended to create the logical files before the copy process starts, because creating the logical files after the physical file has been updated can take significant time, depending on the number of records in the physical file.
Copy program	-	Enter the name of the program that you want to use for copying the records or select GEN to let Rapid Fire generate a copy program for you. For logical files only NONE is allowed.
Copy program library	-	Enter the name of the library where the copy program is stored. Rapid Fire stores a generated copy program in the shadow library.
Conversion program	-	Enter the name of the conversion that you want to use for converting records or select *NONE.
Conversion program library	-	Enter the name of the library where the conversion program is stored.

Area	-	Enter the name of the area. The name must follow the rules for host object names.
Library	-	Enter the name of a production library that you added to the Rapid Fire job beforehand.
Library list	-	Enter the name of the library list that you want to use for compiling the objects of the shadow environment.
Library CCSID	-	Enter the CCSID of the files of the production library. Rapid Fire executes the copy job with that CCSID to properly create the shadow environment. The CCSID is also assigned to the copy job while copying data.
Command extension	-	Add additional parameters that are added to the compile command that is used for compiling the file in the shadow environment. For example, if the base command was CRTPF, then parameter SRTSEQ could be different for each area.