Download Dollar Universe Manager for PeopleSoft User Guide

Dollar Universe Manager for
PeopleSoft
User Guide
Version: 6.7.01
Publication Date: 2016-09
Automic Software GmbH
ii | Copyright
Copyright
Automic® and the Automic logo® are trademarks owned by Automic Software GmbH (Automic). All
such trademarks can be used by permission only and are subject to the written license terms. This
software/computer program is proprietary and confidential to Automic Software and is only available
for access and use under approved written license terms.
This software/computer program is further protected by copyright laws, international treaties and other
domestic and international laws and any unauthorized access or use gives rise to civil and criminal
penalties. Unauthorized copying or other reproduction of any form (in whole or in part), disassembly,
decompilation, reverse engineering, modification, and development of any derivative works are all
strictly prohibited, and any party or person engaging in such will be prosecuted by Automic Software.
No liability is accepted for any changes, mistakes, printing or production errors. Reproduction in whole
or in part without permission is prohibited.
© Copyright Automic Software GmbH. All rights reserved.
Other names may be trademarks of their respective holders.
Dollar Universe Manager for PeopleSoft User Guide | iii
Contents
1 Release Notes ...................................................................................................................... 5
2 Introduction .......................................................................................................................... 6
2.1 Overview ......................................................................................................................... 6
2.2 Features .......................................................................................................................... 6
2.2.1 Job Submission ........................................................................................................ 7
2.2.2 Job Monitoring .......................................................................................................... 7
2.3 Architecture ..................................................................................................................... 7
3 Installation ............................................................................................................................ 9
3.1 Prerequisites ................................................................................................................... 9
3.2 Installing Dollar Universe Manager for PeopleSoft ......................................................... 9
3.3 Upgrading Dollar Universe Manager for PeopleSoft ...................................................... 9
4 Configuration ..................................................................................................................... 10
4.1 Configure the Manager ................................................................................................. 10
4.1.1 Database Users ...................................................................................................... 10
4.1.2 PeopleSoft Batch User in PeopleSoft ..................................................................... 11
4.1.3 Configuration of the PeopleSoft Processes ............................................................ 11
4.2 Administering the Manager for PeopleSoft ................................................................... 11
4.2.1 User License ........................................................................................................... 11
4.2.2 Declare the Environment ........................................................................................ 12
4.2.3 Start / Stop the Manager for PeopleSoft ................................................................ 12
4.3 Manager for PeopleSoft Node Settings ........................................................................ 12
4.4 Manager for PeopleSoft Logging .................................................................................. 14
4.4.1 SQR Traces ............................................................................................................ 14
5 UniViewer Console ............................................................................................................ 15
5.1 Sample Uproc ............................................................................................................... 15
5.1.1 Uproc Definition ...................................................................................................... 15
5.1.2 Uproc Variables ...................................................................................................... 16
5.1.3 Uproc Sample Description ...................................................................................... 19
5.2 Managing PeopleSoft Jobs ........................................................................................... 22
5.2.1 Launch of PeopleSoft Processes ........................................................................... 22
5.2.2 Monitor PeopleSoft Processes ............................................................................... 23
5.2.3 Cancel a PeopleSoft Process (UNIX) ..................................................................... 23
5.2.4 Re-synchronize on a PeopleSoft Process .............................................................. 24
5.2.5 Re-launch a PeopleSoft Process ........................................................................... 24
6 Commands ......................................................................................................................... 25
6.1 Trigger a PeopleSoft Process ....................................................................................... 25
6.1.1 Items ....................................................................................................................... 26
6.1.2 Example .................................................................................................................. 28
6.2 Synchronize on a PeopleSoft Process ......................................................................... 28
6.2.1 Items ....................................................................................................................... 28
iv | Contents
6.2.2 Example .................................................................................................................. 29
6.3 Cancel a PeopleSoft Process (UNIX) ........................................................................... 29
6.3.1 Items ....................................................................................................................... 29
6.3.2 Example .................................................................................................................. 30
6.4 Add/Update a Database User ....................................................................................... 30
6.4.1 Items ....................................................................................................................... 30
6.4.2 Example .................................................................................................................. 30
6.5 List the Database Users ............................................................................................... 30
6.5.1 Example .................................................................................................................. 30
6.6 Delete a Database User ............................................................................................... 31
6.6.1 Items ....................................................................................................................... 31
6.6.2 Example .................................................................................................................. 31
7 Appendices ......................................................................................................................... 32
7.1 PeopleSoft Data Dictionary for Processes ................................................................... 32
7.1.1 Process Type .......................................................................................................... 32
7.1.2 PeopleSoft Job Status ............................................................................................ 32
7.2 Troubleshooting the Manager for PeopleSoft ............................................................... 33
7.2.1 Access to the database user file ............................................................................ 33
8 About Automic Software, Community and Services ...................................................... 34
8.1 Automic Software Company ......................................................................................... 34
8.2 Automic Community...................................................................................................... 34
8.3 Download Center .......................................................................................................... 34
8.4 Technical Support ......................................................................................................... 35
8.5 Training and Services ................................................................................................... 35
Chapter 1 Release Notes | 5
1 Release Notes
The following is the change history. Information on bug-fixes and known errors is available in the
Workload Automation Release Notes and by contacting Automic technical support.
Date
Key Features
2014-11
Dollar Universe user manuals change their look to integrate the Automic world.
2015-02
PeopleTools versions supported by the Manager are 8.49 to 8.53.
6 | Chapter 2 Introduction
2 Introduction
Welcome to the Dollar Universe Manager for PeopleSoft User Guide!
This user manual contains information that is useful for:

Consultants

Dollar Universe users and administrators

PeopleSoft users and administrators
It is assumed that the reader is familiar with Dollar Universe, UniViewer and PeopleSoft (environment
and configuration).
2.1 Overview
This manual describes Dollar Universe Manager for PeopleSoft technical data and features. It details
installation, configuration, administration and usage of the Dollar Universe Manager for PeopleSoft.
To provide coherent overall management of batch processing in the corporate information system,
Dollar Universe proposes integration packages with most standard software solutions. These
integration packages are meant to handle batch jobs delivered by all types of applications, whether inhouse developments or standard software packages.
For PeopleSoft, Dollar Universe Solutions proposes a Dollar Universe Manager for PeopleSoft. The
first objective of the Dollar Universe Manager for PeopleSoft is to manage PeopleSoft batch
operations from Dollar Universe: PeopleSoft process triggering, PeopleSoft process monitoring and
control.
Dollar Universe Manager for PeopleSoft can handle the following types of PeopleSoft processes:
SQR (SQR report and SQR process), COBOL, Crystal Report, Application Engine, nVision (nVision
Report, nVision ReportBook), Cube Builder, HyperCube builder.
Dollar Universe Manager for PeopleSoft can also handle dispatching options of PeopleSoft processes
through PeopleSoft Distribution Agent.
2.2 Features
The Dollar Universe Manager for PeopleSoft provides a set of functions:

A Uproc sample to define and monitor PeopleSoft processes via the UniViewer Console. The
same Uproc sample can manage the different types of PeopleSoft processes (PRCS type):
SQR Report, SQR process, Cobol SQL, Crystal Reports, Application Engine, nVision and
Cube Builder processes.

Commands for use in Uproc scripts to define and monitor PeopleSoft processes.
For PeopleSoft process submission, the Manager ensures:

The synchronization of a PeopleSoft process with the requesting Uproc.

Secure mechanisms, based on a dedicated job log, which records messages exchanged
between Dollar Universe, the command for PeopleSoft and the PeopleSoft process it
launches.
Chapter 2 Introduction | 7
2.2.1 Job Submission
Submission of a PeopleSoft process by Dollar Universe is synchronous: the Dollar Universe Uproc
execution waits for the end of the execution of the PeopleSoft process, until it receives confirmation
from PeopleSoft that the PeopleSoft process has completed.
Commands are detailed in the chapter “Commands” on page 25.
2.2.2 Job Monitoring
PeopleSoft process completion codes are:

Retrieved by the command for PeopleSoft which queries the PeopleSoft tables,

Returned to the Dollar Universe Uproc execution that requested the launch of the PeopleSoft
process.
On UNIX, if the execution of the source Uproc is stopped for whatever reason (operator or external
intervention), Dollar Universe requests the command to stop the corresponding PeopleSoft process
and waits for the PeopleSoft process to terminate before halting the corresponding Uproc (this feature
is not available for the Manager for PeopleSoft on Windows).
2.3 Architecture
Dollar Universe Manager for PeopleSoft enables a launch of a PeopleSoft process to be requested
from within a Uproc running under Dollar Universe.
Communication between the commands of the Manager for PeopleSoft and PeopleSoft is managed
by database connections and database requests.
The execution of the command of the Manager for PeopleSoft within a Uproc script inserts the
PeopleSoft process description in the PeopleSoft database tables so that the PeopleSoft internal
scheduler (PeopleSoft Process Scheduler) can take the new requested execution into account.
As soon as the command is informed of the PeopleSoft process completion, it wakes the Dollar
Universe scheduler and records the completion of the Uproc in the Dollar Universe event base.
Six components are involved in the architecture:

Dollar Universe: the job scheduling solution, designed to automate enterprise batch jobs, with
comprehensive user interfaces to define and monitor jobs across all the network, for all types
of applications, for all types of Operating systems.

Dollar Universe Manager for PeopleSoft: Dollar Universe commands meant to handle the
submission and supervision of PeopleSoft processes of the following types: SQR, COBOL,
Crystal Report, Application Engine, nVision and Cube Builder.

PeopleSoft Process Scheduler: PeopleSoft component meant to handle requests for
elementary PeopleSoft processes by querying, in a cyclical manner, specific tables in the
PeopleSoft database.

PeopleSoft Process Monitor: PeopleSoft component meant to serve as a standard
supervision console for PeopleSoft processes.

PeopleSoft Database Server: PeopleSoft database managed by a RDBMS (ORACLE, SQL
Server, etc.). The PeopleSoft Process Scheduler works with the tables containing the
definition of processes that are to be triggered by Process Scheduler.

PeopleSoft process: PeopleSoft program of the following type: SQR, COBOL, Application
Engine, etc. Irrespective of its type, a process is systematically executed in a single process
within the host operating system (UNIX or Windows). This process is identified in the
PeopleSoft database.
8 | Chapter 2 Introduction
Figure 1 : Outline of interface with PeopleSoft
The process to launch a process in PeopleSoft, starting from the execution of an Uproc in Dollar
Universe, follows several steps involving the above listed components:

The Manager for PeopleSoft command is triggered from a Uproc execution. Parameters to
describe the PeopleSoft process to be launched are passed to the command by Dollar
Universe.

The Manager for PeopleSoft command submits the PeopleSoft process by inserting
appropriate information in PeopleSoft database tables, in accordance with the parameters
that were passed. The process instance (PRCSINSTANCE), which represents the PeopleSoft
process identifier, is computed by the command of the Manager for PeopleSoft. The process
description is inserted in the PSPRCSRQST table with a run status attribute set to ‘Initiated’.
Then the command of the Manager for PeopleSoft waits for PeopleSoft Process Scheduler to
trigger the PeopleSoft process.

PeopleSoft Process Scheduler polls on a cyclical basis the PSPRCSRQST table and
searches a new line intended for it (actually all the processes with a run status set to
‘Initiated’). It finds the line that was inserted by the command of the Manager for PeopleSoft
and retrieves the batch parameters.

PeopleSoft Process Scheduler triggers the associated PeopleSoft process and updates the
run status of the process in the PSPRCSRQST table.

The command of the Manager for PeopleSoft polls, on a cyclical basis, the PSPRCSRQST
table and searches for the process instance corresponding to the submitted PeopleSoft
process. The command enters a test loop on the run status.

Prior to completing, the PeopleSoft process (if it is an API-aware process) updates the
PSPRCSRQST table to inform of either success or failure of the process.

The command of the Manager for PeopleSoft detects that the PeopleSoft process has ended
and retrieves the process status in the PSPRCSRQST table. This status is passed to Uproc
execution using standard exit codes: 0 for success, 1 for failure.
Specific to UNIX
If a stop order is requested for the Uproc execution from the Dollar Universe user interface, then a
specific procedure will be launched in order to transmit the execution stop order to PeopleSoft
Process Scheduler, if the PeopleSoft process is still active. The stop request is intercepted by the
command of the Manager for PeopleSoft and the order is transmitted to PeopleSoft. Then the
command of the Manager for PeopleSoft continues to poll the PSPRCSRQST table until the
PeopleSoft process is really stopped. As a conclusion, an aborted status is sent to Dollar Universe.
This mechanism is not available for Windows platforms.
Chapter 3 Installation | 9
3 Installation
3.1 Prerequisites
For more information on supported operating systems and compatibility with other Dollar Universe
products, refer to the compatibility matrix which can be found on the Customer Service website in the
content tab.
Dollar Universe and the Manager for PeopleSoft have to be installed on a server where a PeopleSoft
Process Scheduler is available. The Manager for PeopleSoft installed on a server will only manage
PeopleSoft processes of the local Process Scheduler.
The Dollar Universe Manager for PeopleSoft runs with PeopleTools software components.
PeopleTools versions supported by the Manager are 8.49 to 8.53.
3.2 Installing Dollar Universe Manager for
PeopleSoft
The Manager makes part of Dollar Universe 6 and does not require additional installation steps to be
performed. However, configuration is required before you start implementing the integration with the
PeopleSoft instance.
The installation procedure creates a subdirectory called bin_psoft in the bin directory of the Dollar
Universe Company. The Dollar Universe Manager for PeopleSoft commands are located in this
subdirectory.
The installation procedure creates a subdirectory called data_psoft in the data directory of the Dollar
Universe Company.
A Uproc sample (psoft_template_*.clint) is available in the bin/clints directory of the Dollar Universe
Company.
3.3 Upgrading Dollar Universe Manager for
PeopleSoft
The upgrade of Dollar Universe Manager for PeopleSoft from Dollar Universe V5 to Dollar Universe
V6 Manager for PeopleSoft is described in the Dollar Universe Upgrade Manual V5 to V6.
Dollar Universe V6 Manager for PeopleSoft is upgraded once the Dollar Universe V6 is upgraded.
10 | Chapter 4 Configuration
4 Configuration
Before integrating Dollar Universe with PeopleSoft, several tasks must be performed:

Define at least one database user that will be used to connect to the PeopleSoft database.
You can use an existing database account or create a new one.

Install a valid license on the Dollar Universe node.

Update the node settings dedicated to the Manager,
These tasks are details hereafter.
4.1 Configure the Manager
4.1.1 Database Users
The Dollar Universe Manager for PeopleSoft must be configured to access PeopleSoft database
tables. At least one DB user must be declared.
4.1.1.1 Using an Existing DB User
The database administrator can provide you with an existing database user account with the
appropriate rights.
Use the command uxaddpsoftuser to declare this DB user with its password. When you specify the
DB user in the Dollar Universe job, you don’t need to specify the password. It will be read by the
Manager when connecting to the database. The password will be never printed.
4.1.1.2 Create a dedicated DB user
A new database user can be specially created for the need of communication from the Dollar
Universe Manager for PeopleSoft.
If a specific database user account is created for Dollar Universe connections, a configuration
procedure has to be launched. You need to be connected to the database as DBA to run the
configuration procedure. If the user does not have enough privileges, please contact your DBA.
In the following, we assume that the DB user name is ‘prcs’.
To configure the database user for the Dollar Universe Manager for PeopleSoft, follow the steps
outlined below:
1. Create the database user for the Dollar Universe Manager for PeopleSoft in your database:
username = prcs, password = prcs. (This is optional if the user account already exists.)
2. Grant the rules PSADMIN and PSUSER to prcs.
3. Grant the rights SELECT, UPDATE and INSERT to prcs on the tables PSPRCSRQST,
PSPRCSRUNTCNTL, PSPRCSQUE, PSPRCSPARMS, PSPRCSRQSTTEXT,
PS_PRCSRQSTDIST, PS_CDM_AUTH, PS_CDM_LIST
4. Grant the rights SELECT and UPDATE to prcs on the table PS_PRCSSEQUENCE
5. Grant the rights SELECT to prcs on all the other tables PS*.
6. Connect to the database as prcs.
7. Create synonyms and aliases to access the PeopleSoft database tables. (The same as the
DBA)
Chapter 4 Configuration | 11
8. Connect to the database as the DBA user.
9. Revoke the PSDAMIN rule from the prcs user.
The Dollar Universe Manager for PeopleSoft can now use the prcs user to access the PeopleSoft
database.
On Unix systems the SQL script prcsuser.sql grants permissions to the database user prcs. This
script is located in the subdirectory specified by the node setting UNI_PSOFT_MGR_BIN.
Once the new DB user is created, register this user and password with the command
uxaddpsoftuser.
4.1.2 PeopleSoft Batch User in PeopleSoft
The PeopleSoft batch user is a user created by the DBA in the PeopleSoft database as owner of the
processes submitted in PeopleSoft by Dollar Universe. Therefore this PeopleSoft user must have the
right to submit processes in PeopleSoft.
4.1.3 Configuration of the PeopleSoft Processes
To launch a PeopleSoft job, a Run Control Id and an a PeopleSoft user are mandatory. They must
exist in PeopleSoft.
If these requirements are not fulfilled, the Manager for PeopleSoft commands exit with error, and the
corresponding Dollar Universe job will be considered as Aborted.
4.2 Administering the Manager for PeopleSoft
4.2.1 User License
Use of the Dollar Universe Manager for PeopleSoft is subject to license. The license key must be
declared in the Dollar Universe license file. This file %UNI_DIR_ROOT%\data\u_fali01.txt is created
by the installation procedure. The license can be entered:

Via UniViewer Console: Administration mode > Nodes > Nodes, select the Dollar Universe
node that supports the Manager > Node Settings > License.

or directly via a text editor.
This license is specific to the Dollar Universe node name on which the Manager for PeopleSoft is
located.
The product code is PSF; product version is 6. Enter the valid license, with the following format:
node product version expiration_date key
Example:
DU6_node DOLLAR_UNIVERSE:PSF 6 20201231 0123456789ABCDEF
License keys can be obtained from the Customer Service web site or through your sales contact.
If the license is not correct, the Manager for PeopleSoft will deny any communication to or from the
Dollar Universe node. An error message is displayed in the Dollar Universe log.
12 | Chapter 4 Configuration
4.2.2 Declare the Environment
When Dollar Universe is installed, node settings are defined with default values. Review the main
node settings related to your PeopleSoft instance and update them with valid values. Refer to the
configuration files located in the directories specified by the variables PS_HOME and
PS_CFG_HOME or use the psadmin command.
The node settings related to a PeopleSoft instance are:

UXPSOFT_DIR: this is the value of the PS_HOME variable.

UXPSOFT_DBTYPE: This is the database type. It designates either Oracle or Microsoft SQL
Server.

DBBIN: This is the path to the database binaries. It depends on the database type.

SQRBIN: This is the path to the SQR interpreter.

CBLBIN, TOOLBIN, TOOLBINSRV, CRWRPTPATH, WINWORD: These variables must be
defined if you submit Cobol SQL processes or processes running on Windows.
All the node settings for this Manager are described in the “Manager for PeopleSoft Node Settings” on
page 12.
The commands to manage these variables (unigetvar and unisetvar) are described in the UniViewer
administration manual.
4.2.3 Start / Stop the Manager for PeopleSoft
Dollar Universe Manager for PeopleSoft does not have a dedicated process. It follows the Dollar
Universe starting and stopping rules.
4.3 Manager for PeopleSoft Node Settings
The table below describes the Manager's variables. These variables can be defined in the Node
Settings>Manager for PeopleSoft Dollar Universe node supporting the Manager:
As for Dollar Universe, the Manager's variables are of Install (I), Static (S) or Dynamic (D) type. The
Manager's variables related to Dollar Universe Installation cannot be modified. They are Install type.
The other variables of Static or Dynamic type can be modified with UniViewer Console or with the
unisetvar command. The change in static variables requires the Manager for xxx to be restarted for
the changes to take effect. Dynamic variables are taken into account by the Manager without having
to restart it.
Variable / Label
I/S/D Description
UNI_PSOFT_MGR_BIN
Manager for PeopleSoft root directory
D
Manager binaries directory. Default value:
!UNI_DIR_EXEC!\bin_psoft
UXPSOFT_DIR
PeopleSoft root directory (PS_HOME)
D
PeopleSoft installation directory.
Default value on Windows: C:\PT8.52
Default value on Unix: /appl/peoplesoft/PT8.52
CBLBIN
Path to COBOL executables
D
Default value on Windows: !UXPSOFT_DIR!\cob
Default value on Unix: !UXPSOFT_DIR!/cblbin
SQRBIN
Path to SQR executables
D
Default value on Windows: !UXPSOFT_DIR!\sqrbinw
Default value on Unix:
!UXPSOFT_DIR!/bin/sqr/ORA/bin
TOOLBINSRV
Path to PeopleTools server executables
D
This variable is defined on Windows only.
Default value: !UXPSOFT_DIR!\bin\server\winx86
TOOLBIN
D
Default value on Windows:
Chapter 4 Configuration | 13
Variable / Label
I/S/D Description
Path to PeopleTools executables
!UXPSOFT_DIR!\bin\client\winx86
Default value on Unix: !UXPSOFT_DIR!/bin
CRWRPTPATH
Path to the Crystal Reports output directory
D
This variable is defined on Windows only.
Default value: !UXPSOFT_DIR!\crw
WINWORD
Path to the Microsoft Word executable
D
This variable is defined on Windows only.
For example: C:\Program Files\Microsoft Office\Office
DBBIN
Path to the database drivers
D
Default value on Windows:
C:\oracle\product\11.2.0\Db_1\bin
Default value on Unix:
/appl/oracle/product/11.2.0/dbhome_1/bin/
UNI_ISQRFLAG
Path to Manager for PeopleSoft SQR files
D
Default value on Windows:
-I!UXPSOFT_DIR!\sqr\,!UNI_DIR_EXEC!\bin_psoft\
Default value on Unix:
-I!UXPSOFT_DIR!/sqr/,!UNI_DIR_EXEC!/bin_psoft/
UXZIFSQRFLAG
SQR initialization file path
D
Default value on Windows:
-ZIF!UXPSOFT_DIR!\sqr\pssqr.ini
Default value on Unix:
-ZIF!UXPSOFT_DIR!/sqr/pssqr.unx
UXXCBFLAG
SQR flag
D
SQR flag for Windows only.
Default value: -XCB
UXXMBFLAG
SQR flag
D
SQR flag for Windows only.
Default value: -XMB
UXPSOFT_SQR_EXEC
Program to run SQR scripts
D
Path to the SQR interpreter: sqrw.exe on Windows,
sqr on Unix.
Default value on Windows:
!UXPSOFT_DIR!\sqrbinw\sqrw
Default value on Unix: !SQRBIN!/sqr
UXPSOFT_DBTYPE
Database type
D
Choice between ORACLE (default value) and
SQLSERVER
UXPSOFT_SLEEP_SEC
Maximum waiting time between 2 pollings
(seconds)
D
This time should be equal to twice the process
scheduler polling cycle + 5 seconds.
Default value is 35 seconds.
UXPSOFT_TIMEOUT
D
Maximum time for a PeopleSoft job to complete
(estimation in seconds)
Default value is 3600 seconds.
UXPSOFT_TIMEOUT_WAIT_START
Maximum time for a PeopleSoft process to
start (seconds)
D
Default value is 100 seconds.
UXPSOFT_RETRYQUERY
Maximum number of attempts to connect to the
PeopleSoft database
D
Used when a DB query fails to get the status of a
PeopleSoft process instance.
Default value is 5
UXPSOFT_SLEEPRETRY
Delay between 2 connection retries (seconds)
D
Default value is 10 seconds.
UXPSOFT_USERFILE
User settings to connect to PeopleSoft
Database
D
File to store the DB user names and encrypted
passwords.
Default value on Windows:
!UNI_DIR_DATA!\data_psoft\psoftuser.ini
Default value on Unix:
!UNI_DIR_DATA!/data_psoft/psoftuser.ini
14 | Chapter 4 Configuration
4.4 Manager for PeopleSoft Logging
The Dollar Universe Manager PeopleSoft generates traces to help administrator track and fix
problems.
You can active the trace mode of the Manager by inserting the keyword PSOFT in the Dollar Universe
Node Settings > category Logging > Main log Level (U_LOG_LEVEL).
The history traces are recorded in the log file of Dollar Universe.
4.4.1 SQR Traces
Some of the Dollar Universe tools are SQR scripts that generate SQR error files and log files. The
generated traces are printed in the files named :

Temporary working file :
Psoft_$(S_CODUG)_$(S_ESPEXE)_$(S_PROCEXE)_$(S_NUMLANC).inp

Error file : Psoft_$(S_CODUG)_$(S_ESPEXE)_$(S_PROCEXE)_$(S_NUMLANC).err

Log file : Psoft_$(S_CODUG)_$(S_ESPEXE)_$(S_PROCEXE)_$(S_NUMLANC).log

Output file : Psoft_$(S_CODUG)_$(S_ESPEXE)_$(S_PROCEXE)_$(S_NUMLANC).out
These files are located in the Dollar Universe U_TMP_PATH directory. When a PeopleSoft process is
completed, these files are removed.
Chapter 5 UniViewer Console | 15
5 UniViewer Console
UniViewer Console is the graphic interface that allows the user to configure the Manager and to
manage PeopleSoft processes from within the job scheduler.
In order to submit and monitor PeopleSoft processes, the standard UVC functions are used:

Definition of PeopleSoft processes using Uproc functions: a Uproc sample is delivered for the
types of PeopleSoft processes supported by the Manager: SQR Report and SQR Process,
Cobol SQL, Crystal, Application Engine, nVision and Cube Builder,

Launch of PeopleSoft processes using Dollar Universe Task and Launch functions,

Monitor and control PeopleSoft processes using Jobs Runs functions (job status, log file…).
Manager configuration is done in Administration mode > Nodes >Nodes; refer to paragraph
"Manager for PeopleSoft Node Settings" on page 12.
5.1 Sample Uproc
A Uproc sample is delivered with the Dollar Universe installation. It is stored in the file
psoft_template_unix.clint for sample on Unix and psoft_template_win.clint for sample on Windows.
This file is present in the bin/clints subdirectory of the Dollar Universe Company.
This sample can be used into any area.
The Uproc created from the sample can be configured to target the type of PeopleSoft process to
submit.


On Windows :
o
Application Engine process
o
Cobol SQL process
o
Crystal process
o
nVision Report Book process
o
SQR Report and SQR Process
o
Cube Builder or HyperCube Builder process
On UNIX:
o
Application Engine process
o
Cobol SQL process
o
SQR Report and SQR Process
5.1.1 Uproc Definition
To configure a PeopleSoft process in Dollar Universe:

Create a new Uproc

In the General section of the Uproc definition, click on the From File button located to the
right of the Type drop-down menu.

Select psoft_template_*.clint from the displayed list and click OK.
The Uproc script is then imported and the variables are created.
16 | Chapter 5 UniViewer Console

Set the Uproc variables in the new Uproc to the appropriate values for the target PeopleSoft
process.
The Uproc sample uses Manager for PeopleSoft commands. The execution of this Uproc generates
the execution of the appropriate command to trigger the PeopleSoft process.
The sample can easily be adapted to adjust the number of variables, to update the execution script, to
update the commands used in the execution…
5.1.2 Uproc Variables
After the Uproc is created, the following variables should be adjusted:
Variable name
Description
Type/Format
UxType
Process types in PeopleSoft (SQR Process, SQR Report, COBOL SQL,
Application Engine, Crystal, …)
Text 255c
UxName
Process name known to the PeopleSoft Process Scheduler panel. The
value of this variable is case sensitive.
Text 255c
UxOprId
PeopleSoft submission account (user), for example VP1
Text 255c
UxRunCtrlId
Run control Id defined for the process in PeopleSoft. This variable
specifies the PeopleSoft execution applicative environment. Both
UxRunCtrlId and UxOprId define the list of parameters needed for the
batch execution and the execution context.
Text 255c
UxDbaseUser
Database user (ORACLE for example).This user and password must be
declared in the file defined by the UXPSOFT_USERFILE node settings.
To declare the user and password, execute the uxaddpsoftuser
command . Refer to section “"Add/Update a Database User on page 30”.
Text 255c
UxDbaseSid
Database instance name that contains the PeopleSoft database.
Text 255c
PSCHED
Process Scheduler instance that handles the process.
Text 255c
PSSERV
Target Application server name.
Text 255c
OUTDESTTYPE
Output destination type of the file generated by PeopleSoft process.
Text 255c
OUTDESTFORMAT Output format of the file generated by the PeopleSoft process.
Text 255c
OUTDEST
Text 255c
Output destination (a printer name, a mail recipient).
5.1.2.1 Select the Output Destination Type
The OUTDESTTYPE variable must be a numeric value taken from the table below:
Value
Output type
0
Any
1
No output
2
File
3
Printer
4
Window
5
e-mail
6
Web
7
Default
When ‘Web’ is selected as output destination type (OUTDESTYPE = 6), the files generated by the
PeopleSoft process will be transferred by the Distribution Agent to the PeopleSoft Web repository
specified in the PS_SERVERDEFN PeopleSoft database table.
Chapter 5 UniViewer Console | 17
Then the files are removed from the initial location by the Distribution Agent.
If the Distribution Agent is not running when the reports or files are ready to be transferred, the run
status of the PeopleSoft process remains ‘Posting’ waiting for the Distribution Agent to move the
generated files.
5.1.2.2 Select the Output Destination Format
The OUTDESTFORMAT variable must be a numeric value taken from the table below:
Value
Output format
0
Any
1
None
2
Acrobat (*.pdf)
3
Comma delimited (*.csv)
4
HP Format (*.lis)
5
HTML Documents (*.htm)
6
Line Printer Format (*.lis)
7
Lotus 1-2-3 Files (*.wks)
8
Microsoft Excel Files (*.xls)
9
Microsoft Word (*.doc)
10
Postscript (*.lis)
11
Crystal Report (*.rpt)
12
Rich Text File (*.rtf)
13
SQR Portable Format (*.spf)
14
Text Files (*.txt)
15
Other
16
Default
17
XML Format(*.xml)
18
Data Mover Data File (*.dat)
19
Crystal Report Explorer (*.rpt)
20
XMLP
21
Atom
5.1.2.3 Select the Output Destination
Printer
To send the file generated by the PeopleSoft process to a printer:

set the Uproc variable OUTDESTTYPE to 3 (for Printer) and

set the Uproc variable OUTDEST to the name of the printer, for instance : LPT1
Default output printer
If OUTDESTTYPE is set to Printer (value = 3) but no printer name is found for OUTDEST variable
(the OUTDEST variable may be blank), the default printer name is retrieved in PeopleSoft for the run
control id and the PeopleSoft operator id. If no printer was specified for the run control id and operator
id, the command displays an error message ("The selected output type is Printer, but no printer was
found.") and stops immediately. The Dollar Universe job final status is ABORTED.
18 | Chapter 5 UniViewer Console
File
To select the location and name of the file generated by the PeopleSoft process:

set the Uproc variable OUTDESTTYPE to 2 and

set the Uproc variable OUTDEST to the full path name of the file.
OUTDEST may contain space characters and should contain a path where the user has read/write
rights.
Default output directories
If OUTDESTTYPE is set to File (value = 2) but no file is specified for OUTDEST, the output directory
is computed with the %log\Ouput Directory% variable, the process type, the process name
(prcs_name) and the instance number (prcs_instance). The filename will be the default name given by
the PeopleSoft process itself.
For Application Engine processes, the default directory is
<UXPSOFT_DIR_LOG>/AE_<prcs_name>_<prcs_instance>
For nVision, nVision-Report and nVision-ReportBook processes, the default directory is
<UXPSOFT_DIR_LOG>/NVS_<prcs_name>_<prcs_instance>
For Crystal processes, the default directory is
<UXPSOFT_DIR_LOG>/CRW_<prcs_name>_<prcs_instance>
For SQR Reports and SQR Process processes, the default directory is
<UXPSOFT_DIR_LOG>/SQR_<prcs_name>_<prcs_instance>
Email
If OUTDESTTYPE is set to Email (value = 5), the variable OUTDEST must contain at least
an e-mail address. If several email addresses are passed to the PeopleSoft process, use the
character semi-colon as separator. If not e-mail address is passed, the PeopleSoft process
instance ends with error and the Dollar Universe job final status will be aborted.
5.1.2.4 Processes and Destination Types
The following table gives the default output destination types available for the process types. It should
help to fill the Uproc variable OUTDESTTYPE.
Process type
Output destination type
Default
Other
None
None
File
Any
Printer
Any
Email
Any
Web
Any
File
Any
Printer
Any
Email
Any
Web
None
PeopleSoft COBOL
None
None
Crystal Report
File
Any
Printer
Any
Email
Any
Web
None
SQR
Chapter 5 UniViewer Console | 19
Process type
Output destination type
Default
Winword Macro
None
None
Application Engine
File
Any
Web
None
Cube Builder
None
None
nVision
File
Any
Printer
Any
Email
Any
Web
Any
Default
None
5.1.3 Uproc Sample Description
5.1.3.1 Application Engine Process
To run the Application Engine process, the PeopleSoft Process Scheduler executes the psae.exe
program found in the path specified by the TOOLBINSRV variable. The TOOLBINSRV variable is set
in the Manager for PeopleSoft Node Settings.
Example: The following table shows the variables defined for a Uproc that triggers an Application
Engine process in PeopleSoft.
Variable Name
Variable Value
UxType
Application Engine
UxName
AEMINITEST
UxOprId
PTDMO
UxRunCtrlId
JSM
UxDbaseUser
prcs
UxDbaseSid
PT852
PSCHED
PSSERV
PSNT
OUTDESTTYPE
1
OUTDESTFORMAT
1
OUTDEST
The database user ‘prcs’ and password must be defined in PeopleSoft with the command
uxaddpsoftuser.
OUTDESTTYPE and OUTDESTFORMAT may differ according to PeopleSoft version. For example, in
PeopleTools 8.49, OUTDESTTYPE=5 (email) is not available.
5.1.3.2 Cobol SQL Process
The Cobol programs must be stored in the directory specified by the CBLBIN variable. CBLBIN
variable is set in the Manager for PeopleSoft Node Settings. Since Cobol does not produce any
output file the OUTDEST is not defined.
Example: The following table shows the variables defined for a Uproc that triggers a Cobol process in
PeopleSoft.
20 | Chapter 5 UniViewer Console
Variable Name
Variable Value
UxType
COBOL SQL
UxName
PTPDBTST
UxOprId
VP1
UxRunCtrlId
JSM
UxDbaseUser
prcs
UxDbaseSid
PT852
PSCHED
PSSERV
PSNT
OUTDESTTYPE
1
OUTDESTFORMAT
1
OUTDEST
5.1.3.3 Crystal Report Process
To run a Crystal Report process, the PeopleSoft Process Scheduler executes the pscrrun.exe
program found in the path specified by the TOOLBIN variable. The generated reports will be located
in the directory specified by the variable CRWRPTPATH.
The DBBIN variable must be correctly set. CRWRPTPATH and DBBIN are set in the Manager for
PeopleSoft Node Settings.
Example: The following table shows the variables defined for a Uproc that triggers a Crystal Report
process in PeopleSoft.
Variable Name
Variable Value
UxType
Crystal
UxName
XRFWIN
UxOprId
VP1
UxRunCtrlId
JSM
UxDbaseUser
prcs
UxDbaseSid
PT852
PSCHED
PSSERV
PSNT
OUTDESTTYPE
6
OUTDESTFORMAT
11
OUTDEST
5.1.3.4 nVision Process
To run nVision, nVision-Report or nVision-ReportBook processes, the PeopleSoft Process Scheduler
executes the psnvs.exe program found in the path specified by the TOOLBIN variable. The DBBIN
variable must be correctly set. TOOLBIN and DBBIN are set in the Manager for PeopleSoft Node
Settings.
Select the kind of nVision process
Chapter 5 UniViewer Console | 21
To run a…
Enter this value for UxType (case sensitive)
nVision process
nVision
nVision-Report process
nVision-Report
nVision-ReportBook process
nVision-ReportBook
Example: The following table shows the variables defined for a Uproc that triggers a nVision process
in PeopleSoft.
Variable Name
Variable Value
UxType
nVision
UxName
RPTBOOK
UxOprId
VP1
UxRunCtrlId
JSM
UxDbaseUser
prcs
UxDbaseSid
PT852
PSCHED
PSSERV
PSNT
OUTDESTTYPE
2
OUTDESTFORMAT
8
OUTDEST
5.1.3.5 SQR Process
Select the kind of SQR process
To run a…
Enter this value for UxType (case sensitive)
SQR Report process
SQR Report
SQR Process
SQR Process
Example: The following figure shows the variables predefined for a Uproc that triggers a SQR Report
or SQR Process in PeopleSoft.
Variable Name
Variable Value
UxType
SQR Process
UxName
XRFWIN
UxOprId
VP1
UxRunCtrlId
JSM
UxDbaseUser
prcs
UxDbaseSid
PT852
PSCHED
PSSERV
PSNT
OUTDESTTYPE
2
OUTDESTFORMAT
2
OUTDEST
SQR Process Uproc uses the SQR command line.
22 | Chapter 5 UniViewer Console
5.1.3.6 Cube Builder Process
Select the kind of Cube Builder process
To run a…
Enter this value for UxType (case sensitive)
Cube Builder process
Cube Builder
HyperCube Builder process
HyperCube Builder
Example: The following figure shows the variables predefined for a Uproc that triggers a Cube Builder
or HyperCube Builder process in PeopleSoft.
Variable Name
Variable Value
UxType
Cube Builder
UxName
PSBLDHC
UxOprId
VP1
UxRunCtrlId
JSM
UxDbaseUser
prcs
UxDbaseSid
PT852
PSCHED
PSSERV
PSNT
OUTDESTTYPE
1
OUTDESTFORMAT
1
OUTDEST
5.2 Managing PeopleSoft Jobs
5.2.1 Launch of PeopleSoft Processes
To launch a PeopleSoft process, the appropriate Uproc should be launched:

Using a Dollar Universe scheduled task and the Dollar Universe engines. Uproc variables can
be changed during the task definition.

Using the Dollar Universe Launches functions and the action “New run”. Uproc variables can
be changed during the launch definition.
In the following, it is assumed that the user knows how to create a Uproc from a sample Uproc. Refer
to the section “Sample Uproc” on page 15 for details on how to create a Uproc from a sample Uproc
into Dollar Universe.

Create a Uproc from a sample Uproc psoft_template_*.clint.

Update the variables of the new Uproc: you must fill in the name of the program to launch
(UxName), the PeopleSoft user (UxOprId), the run control id (UxRunCtrlId), the database user
(UxDbaseUser), the database instance name (UxDbaseSid).
Update also the specific variables according to the type of PeopleSoft process.

Declare the database user and password in the users file with the uxaddpsoftuser command
. Refer to section “"Add/Update a Database User on page 30”.

Create a Dollar Universe launch to execute the new Uproc. You can also modify the values of
the variables before launching the Uproc. These values will override the Uproc variables
values.
Chapter 5 UniViewer Console | 23
Example of a Uproc log file for submitting an Application Engine:
_!================================================
_!**
$!** PROCEDURE .. : PSOFT_APP
$!** VERSION .....: 000
$!** EXECUTION .. : 0000003
_!**
_!** PROCESS DATE : 07/12/2012
_!**
_!-----------------------------------------------$!** PARAMETERS. : None
_!-----------------------------------------------_!** VARIABLES
UxType
:Application Engine
UxName
:AEMINITEST
UxOprId
:PTDMO
UxRunCtrlId
:JSM
UxDbaseUser
:prcs
UxDbaseSid
:PT852
PSCHED
:
PSSERV
:PSNT
OUTDESTTYPE
:0
OUTDESTFORMAT
:0
OUTDEST
:
_!================================================
20120712132606
Pass Step : 00
"Step 00"
PeopleSoft job successfully inserted in the Process Scheduler tables.
Waiting for the end of the PeopleSoft job...
The process instance of the PeopleSoft job is PRCSINSTANCE=607
PeopleSoft Job Completed.
"PSOFT_APP : Normal completion"
5.2.2 Monitor PeopleSoft Processes
As soon as the starting date-time has been reached for the launch, the Dollar Universe engines will
take into account this job. After having checked all the job pre-requisites, the job changes to a
running status in Dollar Universe. After the execution phase, the completed or aborted status is
displayed and all of the following actions can be undertaken:

Access to the job variables definition

On UNIX, ability to cancel the job execution

Access to the job log, including the PeopleSoft process log and a logging of all possible
problems found in a PeopleSoft process submission

Access to the Dollar Universe history trace

Rerun the execution

Purge the record from the job monitor
5.2.3 Cancel a PeopleSoft Process (UNIX)
With the Uproc sample provided, the activation of the option “Cancel” in the Job Runs will cancel the
execution of the corresponding PeopleSoft process.
The Dollar Universe process will wait for the end of PeopleSoft process before exiting.
The job will receive an “Aborted” status in Dollar Universe.
24 | Chapter 5 UniViewer Console
5.2.4 Re-synchronize on a PeopleSoft Process
With the Uproc sample provided, if for any reason (technical synchronization problem for instance),
the Dollar Universe job displayed an aborted status, but the process in PeopleSoft is still active, it is
possible to resynchronize on the associated PeopleSoft process. This can be done using the “Rerun”
option in the Job Runs with the step number 99.

If the process is still active in PeopleSoft, then the Dollar Universe job will wait for it to end.

If the process is finished in PeopleSoft, then the Dollar Universe job will retrieve its completion
status and log file.
5.2.5 Re-launch a PeopleSoft Process
With the Uproc sample provided, if the Dollar Universe job displays an aborted status, and the
PeopleSoft has to be re-launched, it is possible to re-launch the PeopleSoft process execution
associated Dollar Universe job. This can be done using the “Rerun” option in the Job Runs with the
step number 98.
Using this feature, the PeopleSoft process will be rerun once more as a new process instance.
Chapter 6 Commands | 25
6 Commands
The Dollar Universe commands make it possible to manage PeopleSoft processes from within the job
scheduler.
uxstrpsoft
Triggers a PeopleSoft process in synchronous or asynchronous mode
uxsynpsoft
Synchronization on a PeopleSoft process that was launched by Dollar Universe or that
was launched by PeopleSoft itself
uxendpsoft
Cancel a PeopleSoft process that was launched by Dollar Universe or that was launched
by PeopleSoft itself
Other commands allow PeopleSoft database connection users and their passwords to be declared
and then saved in the file in the UXPSOFT_USERFILE node settings. Passwords are encrypted.
uxaddpsoftuser
Add / Modify a user and password
uxdelpsoftuser
Delete a user and password
uxlstpsoftuser
List the encrypted users and passwords.
Refer to the Dollar Universe Commands Manual for more details about the commands general
specifications.
The commands described hereafter are located in the directory specified by the node setting
UNI_PSOFT_MGR_BIN.
Keywords for options are case insensitive. For example, the patterns UxType=”SQR Process” or
uxtype=”SQR Process” are both valid syntaxes.
6.1 Trigger a PeopleSoft Process
Dollar Universe provides a command for triggering PeopleSoft process from the Uproc CL
environment.
The process may be triggered with its pre-defined parameters; alternatively other parameters,
described below, may be substituted.
Command format is as follows:
uxstrpsoft
Item
Format
uxtype=
String
nowait
uxname=
String
uxoprId=
String
uxrunctrlid=
String
uxdbaseuser=
String
uxdbasesid=
String
numlanc=
7c Integer
psserv=
String
outdesttype=
1c
outdestformat=
2c
outdest=
String
Default
26 | Chapter 6 Commands
6.1.1 Items
uxtype: Process types in PeopleSoft (SQR, COBOL, Application Engine, Crystal, …). This parameter
must be a value taken from the table:
Process
Type of Process
uxtype
SQR
SQR Report
SQR Report
SQR Process
SQR Process
PeopleSoft COBOL
COBOL
COBOL SQL
Crystal Report
Crystal Report
Crystal
Application Engine
Application Engine
Application Engine
Cube Builder
Cube Builder
Cube Builder
HyperCube Builder
HyperCube Builder
nVision
nVision
nVision-Report
nVision-Report
nVision-ReportBook
nVision-ReportBook
nVision
nowait: Triggers a process in asynchronous mode.
The command returns immediate control to the Uproc once the process has been submitted. It does
not wait for the PeopleSoft process to complete. The process's termination status can be retrieved
using the uxsynpsoft command described below.
If the NOWAIT switch is not supplied the submission will be synchronous. Control will only be returned
to the Uproc when the PeopleSoft process has completed.
On UNIX, if the Uproc containing a synchronous uxstrpsoft is stopped, the cancellation order is
transmitted to the command and to PeopleSoft, which stops the corresponding PeopleSoft process
before canceling the Uproc execution.
uxname: Process name known in the PeopleSoft Process Scheduler panel. The value of this variable
is case sensitive.
uxoprid: PeopleSoft user account.
uxrunctrlid: Run Control Id defined for the process in PeopleSoft.
uxdbaseuser: The database user. This user and password must be declared in the file defined by the
UXPSOFT_USERFILE node settings. To declare the user and password, execute the
uxaddpsoftuser command. Refer to paragraph “"Add/Update a Database User on page 30”.
uxdbasesid: Database instance name that contains the PeopleSoft database.
numlanc: Dollar Universe launch number corresponding to the PeopleSoft process
psserv: Target Application server name.
outdesttype: Output destination type of the PeopleSoft process. This parameter must be a numeric
value taken from the table:
Value
Output type
0
Any
1
No output
2
File
3
Printer
4
Window
5
e-mail
6
Web
Chapter 6 Commands | 27
Value
Output type
7
Default
When ‘Web’ is selected as output destination type, (i.e. OUTDESTYPE = 6), the files generated by
the PeopleSoft process will be transferred by the Distribution Agent to the PeopleSoft Web repository
specified in the PS_SERVERDEFN PeopleSoft Database table.
Then the files are removed from the initial location by the Distribution Agent.
If the Distribution Agent is not running when the reports or files are ready to be transferred, the run
status of the PeopleSoft process remains ‘Posting’ waiting for the Distribution Agent moves the
generated files.
Refer to section "Select the Output Destination" for more details on the way to use this parameter.
outdestformat: Output format of the PeopleSoft process. This variable must be a numeric value
taken from the table:
Value
Output format
0
Any
1
None
2
Acrobat (*.pdf)
3
Comma delimited (*.csv)
4
HP Format (*.lis)
5
HTML Documents (*.htm)
6
Line Printer Format (*.lis)
7
Lotus 1-2-3 Files (*.wks)
8
Microsoft Excel Files (*.xls)
9
Microsoft Word (*.doc)
10
Postscript (*.lis)
11
Crystal Report (*.rpt)
12
Rich Text File (*.rtf)
13
SQR Portable Format (*.spf)
14
Text Files (*.txt)
15
Other
16
Default
17
XML Format(*.xml)
18
Data Mover Data File (*.dat)
19
Crystal Report Explorer (*.rpt)
20
XMLP
21
Atom
Refer to section "Select the Output Destination Format" for more details on the way to use this
parameter.
outdest: Output destination (a printer name, a mail recipient, a file or a path).
Refer to section "Select the Output Destination Type" for more details on the way to use this
parameter.
If the PeopleSoft process is followed by a distribution using PeopleSoft Distribution Agent, the
uxstrpsoft command will complete successfully if the process is in the “Not posted” state in
PeopleSoft. The command will not wait for the completion of the distribution.
28 | Chapter 6 Commands
6.1.2 Example
The following command:
uxstrpsoft uxtype=”SQR Report” uxname=XRFWIN uxoprid=VP1 uxrunctrlid=Test
uxdbaseUser=prcs uxdbasesid=DEV numlanc=0000096 psserv=PSNT outdesttype=2
outdestformat=2
will trigger the process in synchronous mode with the following characteristics:

Type of PeopleSoft process: SQR Report

Name of the PeopleSoft process: XRFWIN

PeopleSoft Operator Id, i.e. PeopleSoft submission user account: VP1

Run Control Id associated to the PeopleSoft process to be launched: Test

Database connection user: prcs

Database Id: DEV

Dollar Universe launch number (unique) associated to the command execution: 0000096

PeopleSoft Process Scheduler that will manage the process: PS1

Application Server of the PeopleSoft process: PSNT

Destination: the output of the PeopleSoft process is a PDF file
The standard output of the command looks like:
PRCS INSTANCE : 134
PeopleSoft process Submitted successfully
PeopleSoft process Completed
6.2 Synchronize on a PeopleSoft Process
Dollar Universe provides a command used to synchronize a Dollar Universe job with any PeopleSoft
process. The PeopleSoft process on which to synchronize might not have been launched by Dollar
Universe. The PeopleSoft process instance is used to identify the PeopleSoft process on which to
synchronize.
Command format is as follows:
uxsynpsoft
Item
Format
uxdbaseuser=
String
uxdbasesid=
String
numlanc=
7c Integer
psinst=
Integer
Default
6.2.1 Items
uxdbaseuser: the database user. This user and password must be declared in the file defined by the
UXPSOFT_USERFILE node settings. To declare the user and password, execute the
uxaddpsoftuser command. Refer to paragraph “"Add/Update a Database User on page 30”.
uxdbasesid: Database instance name that contains the PeopleSoft database.
Chapter 6 Commands | 29
numlanc: Dollar Universe launch number corresponding to the PeopleSoft process. This parameter is
used to synchronize on a PeopleSoft process launched by Dollar Universe. In this case, the
PeopleSoft process is identified by the Dollar Universe launch number of the Dollar Universe job. This
parameter is incompatible with the psinst parameter.
psinst: PeopleSoft process instance of the PeopleSoft process on which the command has to
synchronize. This parameter is used to synchronize on a PeopleSoft process identified by the
PeopleSoft Process instance. This parameter is incompatible with the numlanc parameter.
If the PeopleSoft process is followed by a distribution using PeopleSoft Distribution Agent, the
uxsynpsoft command will complete successfully if the process is in the “Not posted” state in
PeopleSoft. The command will not wait for the completion of the distribution.
6.2.2 Example
The following command:
uxsynpsoft uxdbaseuser=prcs uxdbasesid=PT852 psinst=135
will wait for the completion of the PeopleSoft process identified by the 135 PeopleSoft Process
Instance.
6.3 Cancel a PeopleSoft Process (UNIX)
Dollar Universe provides on UNIX platforms a command used to cancel a PeopleSoft process. The
PeopleSoft process to cancel might not have been launched by Dollar Universe. The PeopleSoft
process instance is used to identify the PeopleSoft process to cancel.
Command format is as follows:
uxendpsoft
Item
Format
uxdbaseuser=
String
uxdbasesid=
String
numlanc=
7c Integer
psinst=
Integer
Default
6.3.1 Items
uxdbaseuser: the database user. This user and password must be declared in the file defined in the
UXPSOFT_USERFILE node settings. To declare the user and password, execute the
uxaddpsoftuser command. Refer to paragraph “"Add/Update a Database User on page 30”.
uxdbasesid: Database instance name that contains the PeopleSoft database.
numlanc: Dollar Universe launch number corresponding to the PeopleSoft process. This parameter is
used to terminate a PeopleSoft process launched by Dollar Universe. In this case, the PeopleSoft
process is identified by the Dollar Universe launch number of the Dollar Universe job. This parameter
is incompatible with the psinst parameter.
psinst: PeopleSoft process instance of the PeopleSoft process to cancel. This parameter is used to
terminate a PeopleSoft process identified by the PeopleSoft Process instance. This parameter is
incompatible with the numlanc parameter.
30 | Chapter 6 Commands
6.3.2 Example
The following command:
uxendpsoft uxdbaseUser=prcs uxdbasesid=PT852 psinst=136
will cancel PeopleSoft process identified by the 136 PeopleSoft Process Instance.
6.4 Add/Update a Database User
The uxaddpsoftuser command sets the password associated with a database user. This definition is
used by Uprocs and submission accounts for PeopleSoft processes.
If the user already exists in the file defined by the UXPSOFT_USERFILE node settings, the password
is updated with the new value.
Syntax:
uxaddpsoftuser <user> <password>
6.4.1 Items
<user>: name of the PeopleSoft database connection user. The space character is prohibited.
<password>: user password.
6.4.2 Example
The following command:
uxaddpsoftuser prcs secret
User 'prcs' was added/updated in PeopleSoft DB user file (Exit Code: 0)
Registers the database user prcs (password secret) in the file defined by the UXPSOFT_USERFILE
node settings.
6.5 List the Database Users
The command uxlstpsoftuser lists the database users declared in the file referenced to by the
UXPSOFT_USERFILE node settings.
Syntax:
uxlstpsoftuser
6.5.1 Example
The following command:
uxlstpsoftuser
PeopleSoft user file :
C:\DUAS\PEPSO6_vmsdmp8491\data\data_psoft\psoftuser.ini (2 def)
USERNAME
PASSWORD
-------------------------------------------eca
ÕÒßðß¾¾¸´‗õ
prcs
¾¨¾ßõÝ
Chapter 6 Commands | 31
Displays the declared users eca and prcs as well as their encrypted passwords.
6.6 Delete a Database User
The command uxdelpsoftuser allows the declaration of a database user to be deleted.
Syntax:
uxdelpsoftuser <user>
6.6.1 Items
<user>: name of the PeopleSoft database connection user.
6.6.2 Example
The following command:
uxdelpsoftuser eca
User 'eca' was deleted from the PeopleSoft DB user file (Exit Code: 0)
Deletes the user eca from the file defined by the UXPSOFT_USERFILE node settings.
32 | Chapter 7 Appendices
7 Appendices
7.1 PeopleSoft Data Dictionary for Processes
7.1.1 Process Type
The generic process types of PeopleSoft 8.7 are :
Value
Process Type
0
Other
1
SQR
2
PeopleSoft Cobol
3
Crystal Report
4
Winword Macro
5
Application Engine
6
Cube Builder
7
nVision
8
Data Mover
7.1.2 PeopleSoft Job Status
Statuses for a PeopleSoft job are:
Value
Status
1
Cancel
2
Delete
3
Error
4
Hold
5
Queue
6
Initiated
7
Processing
8
Cancelled
9
Success
10
No Success
11
Posted
12
Not Posted
13
Resend
14
Posting
15
Generated
16
Pending
Chapter 7 Appendices | 33
7.2 Troubleshooting the Manager for
PeopleSoft
7.2.1 Access to the database user file
The database user file should be created and maintained by the Dollar Universe administrator with
uxaddpsoftuser and uxdelpsoftuser commands. Check that the Dollar Universe submission
accounts used to execute Uprocs for PeopleSoft can access the database user file in read-write
mode.
If the commands uxlstpsoftuser, uxstrpsoft, uxsynpsoft and uxendpsoft are executed by a Dollar
Universe submission account which cannot open this file in read-write mode, these commands will
end with the exit code 3 (Cannot open file).
34 | Chapter 8 About Automic Software, Community and Services
8 About Automic Software,
Community and Services
This topic introduces the Automic Software company and how to leverage the full potential of our
solutions to you.
You can also obtain Automic documentation online from docs.automic.com.
8.1 Automic Software Company
Automic Software is dedicated to business automation.
Automic is the world's most comprehensive platform in automating businesses. Founded 1985,
Automic pioneered the largest, independent, globally deployed automation platform which powers the
enterprise, application and infrastructure. Now, as the consumerization of IT accelerates, Automic is
re-imagining how organizations integrate next generation service models such as Cloud, DevOps and
Big Data. Today, our software automates tens of millions of operations a day for over 2,000
customers worldwide. We challenge conventional thinking, enabling our customers to be faster,
smarter, in control. Automic – the standard in business automation.
Find out more at our website www.automic.com .
8.2 Automic Community
Want to connect with other Automic users to compare notes or learn how others are tackling problems
that you’re running into?
Talk with other users from around the world to learn how they optimize their business automation with
Automic. Interact with the Automic Team to get ONE Automation Platform tips and tricks straight from
the source.
Join the Automic Community and become an Automic Insider and be among the first to get news
about new products and events, even before they are generally announced!
8.3 Download Center
Make sure that you are using our products to their fullest potential.
The Download Center is the place where you find product downloads, documentation and information
on new releases and hot-fixes about your Automic solution. It’s all in one place: from service hotfixes,
release notes, and all guides. You will also find patch descriptions, known bugs or workarounds.
Chapter 8 About Automic Software, Community and Services | 35
8.4 Technical Support
We have a support team you can trust.
Our team of professionals is ready to support you, anytime and anywhere. Three support centers
located in Europe, the United States, and Asia Pacific build the core of the Automic support
organization.
Our Technical Support Team makes sure that your closest Automic experts are never more than a
few hours flight away, no matter on which continent your subsidiaries and data centers are located.
Automic Software is designed to provide global connectivity for international companies. You are
employing Automic software on a global scale and therefore you can expect global service.
8.5 Training and Services
Do you want to learn even more about Automic solutions?
We offer a range of training options on how to get the most out of your Automic solution. Depending
on your location, either open training sessions at an Automic Software Service Center, or
personalized training sessions at your company's site suits best. Visit the training site and get detailed
information about currently offered courses.