Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. infacmd dps Command Reference
  16. infacmd edl Command Reference
  17. Infacmd es Command Reference
  18. infacmd ihs Command Reference
  19. infacmd ipc Command Reference
  20. infacmd isp Command Reference
  21. infacmd ldm Command Reference
  22. infacmd mas Command Reference
  23. infacmd mi Command Reference
  24. infacmd mrs Command Reference
  25. infacmd ms Command Reference
  26. infacmd oie Command Reference
  27. infacmd ps Command Reference
  28. infacmd pwx Command Reference
  29. infacmd roh Command Reference
  30. infacmd rms Command Reference
  31. infacmd rtm Command Reference
  32. infacmd sch Command Reference
  33. infacmd search Command Reference
  34. infacmd sql Command Reference
  35. infacmd tdm Command Reference
  36. infacmd tools Command Reference
  37. infacmd wfs Command Reference
  38. infacmd ws Command Reference
  39. infacmd xrf Command Reference
  40. infacmd Control Files
  41. infasetup Command Reference
  42. pmcmd Command Reference
  43. pmrep Command Reference
  44. Working with pmrep Files

Command Reference

Command Reference

pmcmd Return Codes

pmcmd Return Codes

In command line mode, pmcmd indicates the success or failure of a command with a return code. Return code “0” indicates that the command succeeded. Any other return code indicates that the command failed.
Use the DOS or UNIX echo command immediately after running a pmcmd command to see the return code for the command:
  • In a DOS shell: echo %ERRORLEVEL%
  • In a UNIX Bourne or Korn shell: echo $?
  • In a UNIX C shell: echo $status
The following table describes the return codes for pmcmd:
Code
Description
0
For all commands, a return value of zero indicates that the command ran successfully. You can issue the following commands in the wait or nowait mode: starttask, startworkflow, aborttask, and abortworkflow. If you issue a command in the wait mode, a return value of zero indicates the command ran successfully. If you issue a command in the nowait mode, a return value of zero indicates that the request was successfully transmitted to the Integration Service, and it acknowledged the request.
1
Integration Service is not available, or pmcmd cannot connect to the Integration Service. There is a problem with the TCP/IP host name or port number or with the network.
2
Task name, workflow name, or folder name does not exist.
3
An error occurred starting or running the workflow or task.
4
Usage error. You passed the wrong options to pmcmd.
5
An internal pmcmd error occurred. Contact Informatica Global Customer Support.
7
You used an invalid user name or password.
8
You do not have the appropriate permissions or privileges to perform this task.
9
Connection to the Integration Service timed out while sending the request.
12
Integration Service cannot start recovery because the session or workflow is scheduled, waiting for an event, waiting, initializing, aborting, stopping, disabled, or running.
13
User name environment variable is set to an empty value.
14
Password environment variable is set to an empty value.
15
User name environment variable is missing.
16
Password environment variable is missing.
17
Parameter file does not exist.
18
Integration Service found the parameter file, but it did not have the initial values for the session parameters, such as $input or $output.
19
Integration Service cannot resume the session because the workflow is configured to run continuously.
20
A repository error has occurred. Make sure that the Repository Service and the database are running and the number of connections to the database is not exceeded.
21
Integration Service is shutting down and it is not accepting new requests.
22
Integration Service cannot find a unique instance of the workflow/session you specified. Enter the command again with the folder name and workflow name.
23
There is no data available for the request.
24
Out of memory.
25
Command is cancelled.


Updated August 15, 2019


Explore Informatica Network