PATH

PATH defines the search path for REXX execs.

Read syntax diagramSkip visual syntax diagram PATH diridpdsid
Note: The SET command (without parameters) is used to retrieve the current path setting.

Operands

dirid
specifies one or more fully qualified REXX File System directories that are searched when you are attempting to locate an exec to be executed.

A full RFS directory ID starts with a pool ID and is in the form: POOL1:\dirid1\...\diridn

When more than one directory ID is specified, a blank is used to separate them.

pdsid
specifies one or more MVS partitioned dataset names.

Return codes

0
Normal return
625
Error retrieving path information
626
Invalid RFS directory name
627
Invalid PDS name
628
Error setting RESULT value
629
Invalid dataset name
630
Error storing path information
631
No path currently defined
632
Resulting PATH contains no RFS directories or PDS names

Examples

'PATH POOL1:\USERS\USER2 POOL2:\USERS\USER2\PROJECT1'
This example shows that the directories in this list are searched in the order specified (from left to right). 
'PATH MYUSERID.REXX1.EXECS MYUSERID.REXX2.EXECS'

This example shows you that the search is started with the first partitioned dataset.

Note:
  1. The dirids and pdsids can be mixed in a single PATH statement.
  2. You can create a very long PATH directory list by concatenating strings together into a variable, and then specifying this variable on the PATH command.
  3. PATH command definitions are not carried across CICS® restarts. To change a PATH definition permanently, insert a PATH command into your PROFILE exec in the base directory for your user ID.
  4. The PATH command is not cumulative, that is, the last PATH command replaces the previous PATH definition.
  5. If dirid or pdsid is not specified, the users current working path is retrieved and placed in the REXX special variable RESULT.
  6. If you receive a non-zero return code, the contents of the RESULT special variable are unpredictable.