Version 4.5.2
 —  Terminal Emulation  —

Transferring Natural Objects

Using the Natural Object Handler, you can transfer data from and to different platforms.

This document covers the following topics:


Transfer Tasks

Transfer tasks can be used on all platforms. A prerequisite is that Natural Version 4.1 or above is installed.

The files created with the transfer tasks can be used directly with the Object Handler (and vice versa).

When Natural Security is active, the security settings for the Object Handler apply.

Natural work file 7 is always used.

The following Entire Connection tasks are available:

Task Description
DSYSTRANS Download Natural source code to a PC.
NATLOADD Load a Natural DDM from a PC. Natural and the TP monitor must be in lower-case mode.
NATLOADO Load a Natural object from a PC. Natural and the TP monitor must be in lower-case mode.
NATUNLDD Unload a Natural DDM to a PC. Natural and the TP monitor must be in lower-case mode.
NATUNLDO Unload a Natural object to a PC. Natural and the TP monitor must be in lower-case mode.
USYSTRANS Upload Natural source code from a PC.

The above sample transfer tasks show how the Object Handler can be used. These tasks can be modified according to your requirements. See the Natural documentation for further information on the Object Handler.

The syntax for the transfer tasks is described below.

DSYSTRANS: Download Natural Source Code to a PC

DSYSTRANS parm1 parm2 parm3

parm1 is the Natural program name. You can also use the wildcard characters "*" and "?" to specify several program names.

parm2 is the name of the Natural library in which the source code is stored.

parm3 is the PC file name without the extension. The extension .trn is automatically added.

NATLOADD: Load a Natural DDM from a PC

NATLOADD parm1 parm2

parm1 is the DDM name. You can also use the wildcard characters "*" and "?" to specify several DDM names.

parm2 is the PC file name without the extension. The extension .sag is automatically added.

NATLOADO: Load a Natural Object from a PC

NATLOADO parm1 parm2 parm3 parm4

parm1 is the object name. You can also use the wildcard characters "*" and "?" to specify several object names.

parm2 is the name of the Natural library in which the object is stored.

parm3 is the name of the Natural library into which the object is loaded.

parm4 is the PC file name without the extension. The extension .sag is automatically added.

NATUNLDD: Unload a Natural DDM to a PC

NATUNLDD parm1 parm2

parm1 is the DDM name. You can also use the wildcard characters "*" and "?" to specify several DDM names.

parm2 is the PC file name without the extension. The extension .sag is automatically added.

NATUNLDO: Unload a Natural Object to a PC

NATUNLDO parm1 parm2 parm3 parm4

parm1 is the object name. You can also use the wildcard characters "*" and "?" to specify several object names.

parm2 is the name of the Natural library in which the object is stored.

parm3 is the name of the Natural library into which the object is unloaded.

parm4 is the PC file name without the extension. The extension .sag is automatically added.

USYSTRANS: Upload Natural Source Code from a PC

USYSTRANS parm1 parm2 parm3

parm1 is the Natural program name. You can also use the wildcard characters "*" and "?" to specify several program names.

parm2 is the name of the Natural library as used by DSYSTRANS.

parm3 is the PC file name without the extension. The extension .trn is automatically added.

Top of page

Executing a Transfer Task

To execute a transfer task, you must first establish the host connection.

Start of instruction set To establish the host connection and execute a transfer task

  1. Log on to the host using Entire Connection.

  2. Start a Natural session on the host.

  3. If PC=ON was not specified when Natural was started, you must issue the Natural terminal command %+.

  4. Go to the NEXT prompt.

    If the main menu is shown, enter MAINMENU OFF in the Natural command line to go to the NEXT prompt.

  5. In Entire Connection, execute a transfer task.

    There are several possibilities to execute a transfer task:

Top of page

Auditing Data Transfer

If the Audit data transfer check box is marked in the user properties, Entire Connection writes data transfer informationen to the log file <username>.log.

The log file contains the following information:

Example

05/10/2007 09:45:37 Started download of file D:\tmp\Employees.ncd
05/10/2007 09:45:37 Ended   download of file D:\tmp\Employees.ncd; Statistics follow:
05/10/2007 09:45:37          File name: D:\tmp\Employees.ncd
05/10/2007 09:45:37          Status   : Terminated Successfully
05/10/2007 09:45:37          Records  : 220      
05/10/2007 09:45:37          Format   : R02A14
05/10/2007 09:45:37          Buffers  : 3   
05/10/2007 09:45:37          UserID   : USER1     
05/10/2007 09:45:37          Library  : USER1     
05/10/2007 09:45:37          Program  : WPC3    
05/10/2007 09:45:37        End of statistics for download of file D:\tmp\Employees.ncd

Top of page