Open Systems Support and Migrations

#### Search Results

Search

# Open Systems Support and Migrations

PAC is able to support the migration and versioning of objects that are developed under Natural on the Open System platform. PAC uses the Natural Utility SYSTRANS to partially facilitate this process.

This process is only able to accommodate source code coming from the Open System platform, Natural sources may contain Operating Systems specific code, that would be impossible to compile, thus the PAC compile process is ignored for these objects within the PAC mainframe environment. The majority of the migration process for these objects is similar to the Incorporation process used for other PAC recognized objects. The process is delivered as semi-automatic, with the need for a SYSTRANS created formatted workfile to be loaded onto the mainframe platform, in order for the PAC migration event process to be executed.

This document covers the following topics:

- Application Definition

- Status Definition

- Application Status Links

- Migration Process In

- Migration Process Out

- Object Handling

## Application Definition

An application to be used for this process would be defined as any other normal application of type (NAT). This is fully documented in section 5 of this documentation.

## Status Definition

Statuses to be used for this process need to be defined in a similar way as statuses for other applications, with only a few exceptions. The status of type I (incorporation) has to be defined for the base status, that of the initial entry status of the incoming objects. This status has to have a defined Natural library. All other statuses for use with this application can be as normal of types of T (test), M (maintenance) and P (production).

## Application Status Links

Defined statuses for the application should be linked in the normal way. This is fully documented in section 6 of this documentation.

## Migration Process In

This process details the process of migrating Natural Open System objects into PAC.

### Step 1: Create workfile

Create a SYSTRANS format workfile from the Open System platform where the application sources reside.

### Step 2: Transfer workfile to mainframe

Use a recognized transport mechanism (FTP) to transfer the workfile from the Open System platform to the mainframe.

### Step 3: Create / Authorize the PAC migration event

Add a PAC migration event for the Open Systems application with the Incorporation status as the From-Status. The migration list must contain the wildcard selection of (*,*) , in order for the event to migrate-in the whole contents of the workfile (please see Natural Systrans documentation for more details). Authorize the PAC event in the normal way.

Ensure that the event has run-mode set to B (Batch) and that it uses the supplied PAC Job <prefix&gt;_SYSTRANS_MIGRATE_IN.

### Step 4: Submit the PAC migration event

The defined PAC migration event through the PAC Job uses a number of variable parameters. These will be called for when the PAC migration event is submitted.

The parameters are:

@FUSER-FROM | FUSER value for incorporation library
@LIBRARY-FROM | Incorporation library
@SYSTRANS_DSN | Name of SYSTRANS workfile
@VOLSER | Volume Serial of workfile
@DISP | Disposition of workfile

### Step 5: Execution of the PAC migration event

The PAC migration event will now perform the various steps contained within the PAC Job. Please see Job details for more information on this.

The migration event will produce an audit trail as normal for migration events. Upon successful completion of the migration event the Natural Open Systems objects will now be fully versioned within PAC and stored in the PAC ACF file.

## Migration Process Out

This process details the process of migrating Natural Open System objects out of PAC.

### Step 1: Create / Authorize the PAC migration event

Add a PAC migration event for the Open Systems application with the Incorporation status as the To-Status. The migration list objects can now be selected and saved. Authorize the PAC event in the normal way.

Ensure that the event has run-mode set to B (Batch) and that it uses the supplied PAC Job <prefix&gt;_SYSTRANS_MIGRATE_OUT. Applymods 8, 19 and 31 should be used when migrating these objects out of PAC.

### Step 2: Submit the PAC migration event

The defined PAC migration event through the PAC Job uses a number of variable parameters. These will be called for when the PAC migration event is submitted.

The parameters are:

@FUSER-FROM | FUSER value for incorporation library
@LIBRARY-FROM | Incorporation library
@SYSTRANS_DSN | Name of SYSTRANS workfile
@DISP | Disposition of workfile
@VOLSER | Volume Serial of workfile

### Step 3: Execution of the PAC migration event

The PAC migration event will now perform the various steps contained within the PAC Job. Please see Job details for more information on this.

The migration event will produce an audit trail as normal for migration events. Upon successful completion of the migration event the objects will now be contained in the defined workfile.

### Step 4: Transfer workfile to Open System Platform

Use a recognized transport mechanism (FTP) to transfer the workfile from the Mainframe to the Open Systems Platform.

### Step 5: Load objects from Workfile

Perform a SYSTRANS load from the workfile into your Natural system on the Open Systems platform.

## Object Handling

Once the Natural Open Systems objects are migrated into PAC, they can then be handled as per any other PAC controlled object. They can be Archived, Retired, Purged and viewed in the Versioned Objects function.

### On this page

- Application Definition
- Status Definition
- Application Status Links
- Migration Process In
- Migration Process Out
- Object Handling