OSI/FTAM and OSI/APLMGR SCF Reference Manual

SCF Commands for Tandem FTAM
OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001
3-121
TRACE PROCESS Errors
For more information on errors specific to APLMGR (OSIAPLMG errors having
positive error numbers), see Appendix B, SCF Error Messages for the APLMGR
Subsystem. For more information on errors specific to FTAM (OSIFTAM errors having
positive error numbers), see Appendix C, SCF Error Messages for the FTAM
Subsystem. For more information on common SCF error messages (errors having
negative error numbers), see the Subsystem Control Facility (SCF) Reference Manual
(for D-series releases) or the SCF Reference Manual for G-Series Releases.
{ OSIAPLMG E-00814 | OSIFTAM E-00814 }
Trace is not active for $process-name
You attempted to stop a trace (by
specifying the STOP option) or modify a
trace (by omitting both STOP and TO), but
no trace was in progress.
{ OSIAPLMG E-00822 | OSIFTAM E-00822 }
Trace is currently active for $process-name
You attempted to start a trace (by
specifying the TO option) while a trace
was in progress.
SCP E-00010
File System Error: error-number
Call: procedure-name,
File: filename
A file-system error occurred on the file
you specified in the TO filename part
of the TRACE command. For example:
SCP E-00010 File System
Error: 48, Call: OPEN, File:
MYTRACE
means that a security violation occurred
when SCP tried to open the file you
specified as the trace file (MYTRACE).
As another example:
SCP E-00010 File System
Error: 12, Call: OPEN, File:
Trace03
means that the file you specified is already
in use (perhaps a trace is already in
progress and is using that file).
For further information on file-system
errors, see the Guardian Procedure Errors
and Messages Manual.
Error Message Description