Code
|
Specific to PeopleSoft?
|
Description
|
|||
000
|
Successful.
|
||||
001
|
yes
|
Indicates
the command contained a syntax error, see the auto_ps7 Appendix for a recap
of the auto_ps7 command syntax.
|
|||
001
|
Catchall
for general errors, (Miscellaneous errors, such as “divide by zero” and other
impermissible operations).
|
||||
002
|
Indicates
that the back-end server is not available or the EiamAdmin user account
password is invalid.
Misuse
of shell built-ins. Missing keyword or command.
|
||||
003
|
yes
|
The
Adapter changed the runstatus from 6 (INITIATED) or 7 (RUNNING).
If
the runstatus was 6, the program had a serious error during startup, or the
program was not API aware.
If
the runstatus was 7, the program exited without going through the API-aware
routine to update the runstatus in the Process Request table. This may also
indicate that the program aborted and possibly created a core file.
|
|||
008
|
yes
|
The
Adapter received a signal from the AutoSys console or from the command line.
The requested program was killed, and the runstatus was changed to 8 in the
Process Request table.
Or
A
user cancelled an ad hoc job through the ProcessMonitor.
|
|||
010
|
yes
|
The
requested program discovered an error and voluntarily set the runstatus to 10
(FAILURE) instead of 9 (SUCCESS).
|
|||
016
|
yes
|
Unable
to allocate storage for request. Memory allocation error.
|
|||
126
|
Command
invoked cannot execute. Permission problem or command is not an executable.
|
||||
127
|
Command
not found. Possible typo, or problem with the path.
|
||||
128
|
Invalid
argument to exit, (exit takes only integer argument sin the range 0-255)
|
||||
200
|
yes
|
Adapter
license expired.
|
|||
201
|
yes
|
Missing
line in $AUTOUSER/.license
|
|||
202
|
yes
|
Missing
environment variable $AUTOUSER. Either the adapter is being run from the
command line without setting up the AutoSys environment or
there
is a problem within AutoSys.
|
|||
203
|
yes
|
Missing
environment variable $AUTOSERV. Either the adapter is being run from the
command line without setting up the AutoSys environment or there is a problem
with in AutoSys
|
|||
204
|
yes
|
The
key generated using system information does not match the encrypted key in
the $AUTOUSER/.license file.
For
permanent keys, ensure the license key is generated using the same IP address
as that in the license file.
For
temporary keys, ensure that the date is entered exactly as shown, including
leading zeros for month and date.
|
|||
205
|
yes
|
Invalid
expiration date in $AUTOUSER/.license. Format should be MM/DD/YYYY.
|
|||
206
|
yes
|
Error
opening $AUTOUSER/.license. This normally means that the file cannot be found
or the specified user does not have read permission on the file.
|
|||
207
|
yes
|
An
error occurred while trying to connect to an unsupported PeopleTools version.
|
|||
209
|
yes
|
Invalid
command-line switch. The auto_ps7 Command Syntax see the auto_ps7 Appendix
for a recap of the auto_ps7 command syntax.
|
|||
210
|
yes
|
An
error occurred while trying to get the value of environment variable PS_INS
which is specified on the command line. Verify that PS_INS is the name of the
environment variable you have set
up in
auto.profile (UNIX) or the AutoSys Administrator (NT).
|
|||
211
|
yes
|
An
error occurred while trying to execute the requested program.
Verify
that the program has execute permissions.
|
|||
212
|
yes
|
An
error occurred while trying to open a file. If it is an input file, make sure
that the specified path/file exists and that the file has read permissions.
If it is an output file, make sure that the specified directory has execute
and write permissions.
|
|||
213
|
yes
|
A
memory allocation error occurred while trying to create buffers for the
database fields that will be retrieved from the Process Request table.
|
|||
214
|
yes
|
The
oprid must be in the PSOPRDEFN table before that oprid can run a program.
|
|||
215
|
yes
|
This
indicates one of the following:
The
programname on the command line is incorrect.
ü A COBOL program could not be found in $CBLBIN, nor in
$PS_HOME/bin. Verify the $CBLBIN is set correctly.
ü A SQR program could not be found in $PS_SQR, $PS_SQR1, $PS_SQR2,
$PS_SQR3, $PS_SQR4 (UNIX) or in $PSSQR1, $PSSQR2, $PSSQR3, $PSSQR4 (NT).
ü The complete path and programwere specified on the command
line and it is incorrect
|
|||
216
|
yes
|
The
Adapter was unable to determine the PARMLIST for the COBOL SQL or Application
Engine program. A string with at least five slashes was expected.
|
|||
217
|
yes
|
An
error was detected while trying to access PS_PRCSTYPEDEFN. This table has a
row that defines the PARM_LIST for PSRUN.
|
|||
218
|
yes
|
An
error was detected while trying to access PS_PRCSDEFN. This table may have a
row that defines overrides to the PARM_LIST retrieved from PS_PRCSTYPEDEFN.
|
|||
219
|
yes
|
An
error was detected while trying to get a Process Instance number for a job.
|
|||
220
|
yes
|
An
error occurred while trying to execute the autorep program. This program is
executed in order to load the names of existing boxes into memory.
|
|||
221
|
yes
|
An
error occurred while trying to execute the JIL program. This program is
executed in order to feed the definition of the ad hoc job to AutoSys.
|
|||
222
|
yes
|
An
error occurred while trying to execute sqr. Verify that the program is
executable and that SQRDIR points to the directory that has the sqr
executable (not to the directory that has the .sqr file).
|
|||
223
|
yes
|
This
indicates one of the following:
ü For SQR programs, the argument following the -M switch is not a
regular file. Normally it is the allmaxes.max or an equivalent file.
ü The argument following the -I switch is a list of
comma-separated directories. The directories contain the .sqc files included
in SQR programs. At least one item in the list is not a directory.
|
|||
224
|
yes
|
The
environment variable ADHOC_SERVERS is followed by a comma-separated list of
servernamerun's, for example, ADHOC_SERVERS=PSUNX,PSNT. The servernamerun
must have
only
alphanumeric characters as well as underscore. Other characters will cause
this error.
|
|||
225
|
yes
|
A bind
variable of the form :RecordName.ColumnName was found in the command line. An
error was detected while trying to access PS_<RecordName> with a matching
OprId and RunControlId.
|
|||
226
|
yes
|
The
nVision-ReportBook is not defined. Define the ReportBook by:
Go,
PeopleTools, ReportBooks, Use, Report Book Definition, Add
|
|||
227
|
yes
|
An
error was detected while trying to access PS_PRCSTYPEDEFN. This table has a
row that defines the sqrconnectstring, sqrparms (for NT), and sqrflags to be
used in the command line.
|
|||
228
|
yes
|
An
error was detected while trying to access PS_PRCSDEFN. This table may have a
row that defines overrides to the sqrparms and/or the sqrflags.
|
|||
229
|
yes
|
Unable
to connect to the PeopleSoft database in three attempts. Start by contacting
a DBA to determine if all necessary components of the database are
functioning correctly.
|
|||
232
|
yes
|
An
error occurred trying to report a database error. Either the Adapter's memory
is corrupt or the database is no longer accessible.
|
|||
233
|
yes
|
A
database error has occurred.
|
|||
234
|
yes
|
Apparently
PeopleSoft is using a database currently not supported by the Adapter.
|
|||
235
|
yes
|
$ODBCDIR/lib
is missing from the Library Path environment variable. This is usually caused
by not appending the Library Path to itself when setting the value in the
psconfig.sh.
|
|||
236
|
yes
|
You
have a three-tier NT configuration. Add the following line to your
configuration file:
PSOFT_DBTYPE=database
type(ORACLE,SYBASE,DB2,INFORMIX)
PSOFT_DBNAME=name
of database
|
|||
237
|
yes
|
You
must adjust the following lines in your configuration file to point to the
correct path in your registry.
PSOFT_REGT="HKEY_CURRENT_USER\\SOFTWARE\\PEOPLESOFT
\\PEOPLETOOLS\\RELEASE7.5\\STARTUP"
PSOFT_REGPS="HKEY_CURRENT_USER\\SOFTWARE\\PEOPL
SOFT
\\PEOPLETOOLS\\RELEASE7.5\\Process
Scheduler"
Use
regedit at the command line to help you find the correct path.
|
|||
238
|
yes
|
The
runcntlid must be in the PSPRCSRUNCNTL table.
|
|||
241
|
yes
|
One
ormore switches on the command line were followed by incorrect arguments.
|
|||
242
|
yes
|
The
command line is incorrect. Refer to the chapter “Using the Adapter” to
provide the correct arguments.
|
|||
243
|
yes
|
The
Adapter was unable to determine a password for the oprid. The password is
specified in a file specified in .autorc.
|
|||
244
|
yes
|
An
environment variable is incorrect. The variable may be missing, or the value
may be incorrect if a filename or directory was expected.
|
|||
245
|
yes
|
Before
accessing the ODBC library, the Adapter does some preliminary validation of
the contents of the odbc.ini file. Some error has been detected.
|
|||
246
|
yes
|
The
Adapter was unable to process the psconfig.sh file. Either the file was not
found or the Adapter was unable to evaluate a substitution string.
|
|||
247
|
yes
|
An
expected section was not found in the configuration file. Verify that the
section is present and is typed in exactly the same case as indicated in the
error message.
|
|||
248
|
yes
|
There
are multiple -f<dirname>s on the command line to be launched. The
Adapter will not make up filenames for more than one -f. Specify a filename
after each -f.
|
|||
249
|
yes
|
The
LASTPRCSINSTANCE column of the PS_PRCSSYSTEM table has been reset, most
likely by a database restore or by the Process Scheduler GUI. Set it to a
value greater than that shown in the error message.
|
|||
255
|
Exit
status out of range (exit takes only integer args in the range 0-255)
|
||||
260
|
yes
|
Invalid
distribution list syntax specified. The distribution list's format should be
-c "U:userid,... R:roleid,...".
For
example, -c "U:JERRY,BERRY,CARRY R:ROLE1,ROLE2"
|
|||
261
|
yes
|
Invalid
user id or role id specified. Make sure the user id or role id is available
in the PeopleSoft database.
|
|||
262
|
yes
|
The Web
posting directory is not available. Check for the validity of the three-tier
installation. The Web server is not set up correctly.
|
|||
263
|
yes
|
Distribution
node information is not available. Check the Report Node Definition through
the PSTools GUI.
|
|||
264
|
yes
|
OPSYS
is not set in the PS_CDM_DIST_NODE table with the specified DISTNODENAME.
|
|||
265
|
yes
|
FTPDIRECTORY
is not set in the PS_CDM_DIST_NODE table with the specified DISTNODENAME, or
the DISTNODENAME is not correct.
|
|||
266
|
yes
|
FTPADDRESS
is not set in the PS_CDM_DIST_NODE table with the specified DISTNODENAME, or
the DISTNODENAME is not correct.
|
|||
267
|
yes
|
The
system is configured using the FTP method for Web posting, but PSOFT_FTPID is
not set in Adapter's configuration file.
|
|||
268
|
yes
|
The
system is configured using the FTP method for Web posting, but PSOFT_FTPPSWD
is not set in Adapter's configuration file.
|
|||
269
|
yes
|
Distribution
node name is not available.
PSOFT_DISTNODENAME
is not set.
|
|||
Notes:
Exit code information was
taken from:
1) Appendix A, Unicenter
AutoSys Adapter for PeopleSoft User Guide
2) Unicenter AutoSys Job Management Adapter
for PeopleSoft User Guide
