Copying Definitions Using the Command Line

Use the same command line syntax as identified previously to copy definitions.

See Understanding PeopleSoft Application Designer Command Line Parameters.

Use the command line statement for Upgrade Copy processes to:

  • Connect to the source database.

  • Connect to the target database.

  • Copy the project and its objects from the source database to the target database.

    If the same project already exists in the target database, you can set the option to overwrite the older project with the new project.

  • Identify the definition type to copy. By default all definition types in the project are copied unless you set the -OBJ parameter to include only specific definition types or you use the -EXOBJ parameter to specify specific definition types to exclude.

    This table lists how these parameters work together in the command line.

    -OBJ

    -EXOBJ

    Object List

    Example

    No

    No

    All Objects

    Command line does not have either of these parameters

    Object list contains all definition types.

    Yes

    No

    All objects listed in -OBJ parameter

    -OBJ 1,2,3

    Object list contains definition types 1, 2, and 3.

    No

    Yes

    All objects except objects listed in -EXOBJ parameter

    -EXOBJ 1,2,3

    Object list contains all definition types except types 1, 2, and 3.

    Yes

    Yes

    Objects of -OBJ excluding objects of -EXOBJ

    -OBJ 0,1,2,3,4,5 -EXOBJ 3,4,5,6,7

    Object list will contains definition types 0,1 and 2.

Example: Database Copy Process

These are some command line statements for the Database Copy process:

  • Copy the project PPLTOOLS from the source Oracle database, PTDMO, to the target database, PTTST.

  • Log process and error messages to c:\temp\copy.log.

  • Set the commit limit to 150.

    Copy the audit flags and record and index DDLs from the source database.

  • Copy only records, indexes, pages, queries, and process definitions from the project.

  • Do not reset the done flags before initiating the Copy process.

  • Copy only English and Spanish translations.

  • Keep the target origin for permission list, roles and menus.

This is a command line statement that performs the preceding list of tasks.

PSIDE.EXE −HIDE -PJC PPLTOOLS -CT ORACLE -CD PTDMO -CO PTDMO -CP password -TD PTTST -TO PTDMO -TP password -QUIET -LF C:\TEMP\COPY.LOG -CL 150 -AF 0 -DDL 0 -OBJ 0,1,5,10,20 -RST 0 -LNG ENG, ESP -PLRM 1

See Command Line Parameters.

Example: Copy To File Process

These are some command line statements for the Copy to File process:

  • Copy the PPLTOOLS project from the Oracle database, PTDMO, by using the PTDMO user ID, to the local directory c:\temp\export.

    A directory named PPLTOOLS is created in c:\temp\export.

  • Log progress and error messages to c:\temp\copy.log.

This is a command line statement that performs the preceding list of tasks.

PSIDE.EXE −HIDE -PJTF PPLTOOLS -FP c:\temp\export -CT ORACLE -CD PTDMO -CO PTDMO -CP password -QUIET -LF c:\temp\copy.log

See Command Line Parameters.

Example: Copy From File Process

These are some command line statements for the Copy From File process.

  • Copy the PPLTOOLS project to the DB2 UDB for Linux, Unix, and Windows database, PTDMO, by using the user ID PTDMO, from the local directory c:\temp\export.

    A directory named PPLTOOLS must exist under c:\temp\export.

  • Log progress and error messages to c:\temp\copy.log.

This is a command line statement that performs the preceding list of tasks.

PSIDE.EXE −HIDE -PJFF PPLTOOLS -FP c:\temp\export -CT DB2UNIX -CD PTDMO -CO PTDMO -CP password -QUIET LF c:\temp\copy.log

See Command Line Parameters.