Building Your Applications after Migration

The following instructions apply to the first build of the application after migration.

 Caution

Disable your system for the duration of the deployment phase of the build to avoid duplicate LINCSUPPORT libraries appearing in the mix.

To build your migrated specifications, perform the following:

  1. In the Developer release, open the Class View window.

  2. Select all structures and select Validate from the Build menu to validate all logic. This might take some time to complete.

  3. Fix any errors found.

Notes:

  • If your specification contains nested methods that bring data into memory, errors might be reported where an Ispec manipulates the data read in by a method. The errors can be resolved by including a dummy read or by repositioning the logic, which performs the read.

  • If your specification has Min Copies set to a value greater than 0 (zero), the application starts during the reorganization. This stalls the reorganization until the application is manually disabled. Alternatively, you can prevent the application from starting in the first instance by creating a file named, (<usercode>)<system name>/ LEAVEDISABLED on the <dictionary pack>.

After this, you can choose any one of the following methods to build your system.

Rebuilding the System with the Delay Compile and Deploy option

  1. Start a build with the REBUILD option. To queue the deployment on the MCP server, ensure that you select the Delay Compile and Deploy option on the Host Login Dialog and the Deploy Time is set.

    1. Open the Class View window in Developer, then on the Build menu, select ReBuild for the first deployment. You can use Build for subsequent deployments.

    2. It is necessary to stop your system for the duration of the deployment phase of the build. To stop the system after the generate phase and before the compilation and deployment of the system, you should select the Delay Compile and Deploy option to queue the deployment on the MCP server. Also, you should change the Deploy Time to a few hours in advance of the current time or a few hours in advance of the expected completion of the generate phase.

  2. Verify that the generate phase on the client is complete and the deployment of the system is queued on the MCP server.

    The generate phase on the client finishes when the following message appears in the log:

    The System Generate has been delayed until a later time

    You can view the systems queued for deployment from the APPL_BLD server by using the command:

    NA APPL_BLD_<ident> QUEUE

    where, <ident> is the identity of APPL_BLD.

    For default installations of APPL_BLD, <ident> is 70, for example, APPL_BLD_70. The message returned by the QUEUE command is the following list of queued systems:

    17:30:00 on 17/02/2012,Scheduled,System TESTUSER,SAMPLE,TESTPACK^

    Note the number of the system, which is used in step 4 to resume the deployment.

    The queue number for the example system specified earlier is one.

  3. Disable the system.

  4. Resume the queued deployment. From MARC, enter the command,

     NA APPL_BLD_<ident> FORCEQ <n>

    where,

    <ident> is the identity of APPL_BLD.

    For default installations of APPL_BLD, <ident> is 70, for example, APPL_BLD_70. <n> is the number assigned to the queued deployment.

    Use the number you obtained from step 3, for example, from MARC enter:

    NA APPL_BLD_70 FORCEQ 1

    The message returned from this command is similar to:

    Queue entry #1 set to now

  5. If you use non-default MAXWAIT values, reapply them after the system is deployed.

    The default MAXWAIT settings are as follows:

    COMS_LINC_TP30 seconds
LSS 10 seconds

  6. When your application build and reorganization are complete, build all Reports if you have not chosen to automatically build the Reports after the application build.

  7. If you are using System Transfer and Configure for your applications, perform the transfer and configure now.

    Rebuilding the System—Alternate Instructions

    If you do not want to use the Delay Compile and Deploy option to build your system, use the following instructions to build your system after migration.

    1. Disable the system.

    2. Build the system using the REBUILD option.

      Open the Class View window in Developer, then on the Build menu, select ReBuild for the first deployment. You can use Build for subsequent deployments.

    3. Reapply MAXWAIT values.

    4. Build reports with the REBUILD option.

    5. If you are using System Transfer and Configure for your applications, perform the transfer and configure now.

    Updating the System with MCP Runtime Transfer (Excluding RDB Systems)

    1. Build the Source system using one of the instruction sets from the previous steps of Rebuilding the System.

    2. Build the RTU file with Rebuild option.

      You might want to perform this step as part of step 1. Ensure that the Runtime Transfer properties are set correctly before you rebuild the source system.

    3. Perform the mandatory step for Hands Free Configure or Compile Free Configure.

      Notes:

      • The following step is mandatory for transfers using Hands Free Configure and Compile Free Configure.

        1. Disable Target System.

          If you are using Hands Free Configure, the compile phase starts automatically. So, it is necessary to disable the Target System at this point in time.

      • For the transfers that are not using Hands Free Configure or Compile Free Configure, the previous step is optional.

    4. Initiate RTU (Runtime Transfer Utility)

      R $(<runtime usercode>)NGEN28/RTU ON <runtime pack>;

    5. Transfer Startup screen

      Enter the <<segment>> class and configuration sets that are associated with this transfer.

    6. Transfer Selection screen

      • Enter V in the Tfr/Configure All Ispec Code field.

        • Auto initiate configure program field – Enter N in the Auto initiate configure program field if the Target System is not disabled at this point. You should do this whether you use BNA as the transfer medium or not. It is necessary to disable the target system before you deploy it. It is easier to do this if the configure phase is not started automatically.

          Enter V in the Auto initiate configure program field if the Target System is disabled at this point. You are now using BNA as the transfer medium and you want to use Hands Free Configure. If the Target System is still enabled but you want to use Hands Free Configure, perform the tasks in step 3 to disable the Target System and remove the system libraries.

      • Transfer Creation screen.

        Enter V in the Auto initiate of transfer job field. The transfer phase is initiated by RTU.

        Change the other options on this screen as you do for a normal transfer at your site.

      • Selected Transfer screen

        If the Selected Transfer screen appears, set up the options so that both the system and reports are transferred.

      • Transmit the final screen in RTU.

        The transfer phase starts after you transmit the final screen in RTU. Wait until this phase is complete and the transfer files are transferred to the transfer medium.

      • For the transfers that are not using Hands Free Configure and not using Compile Free Configure.

        If the Target system is not disabled already, it must be disabled now.

        1. Disable the Target System

      • Run the Configure Utility for the transfers that do not use Hands Free Configure.

        RUN $RUNTIMETRANSFER/<source config>/<target config>/CONFIGURE
(for an automated configure using a configure configuration set)

        OR

        RUN $RUNTIMETRANSFER/<source config>/CONFIGURE
(for a manual configure using the Configure Utility screens)

      • The Configure Utility initiates the configure phase for transfers that do not use Hands Free Configure. Wait for the configure phase to complete.

       Caution

      Do not start up your application until the build or transfer process is fully completed.