In this section: |
Permanent files include metadata and procedures that were either created before the session by another application or remain after the session is over for use by another application.
Unless a file name is fully qualified with the application name, the search sequence is:
The following commands follow the search path, starting with the application set by the APP HOLDMETA command:
APP HOLDMETA APP1
When a procedure is executed, and referred to by a one-part name
EX ABC
the following is executed
profile.fex in APP1 application
followed by
EX APP1/ABC
If the procedure ABC is not found in APP1, the server follows the standard search path for procedures to find and execute it.
Unless a file name is fully qualified or redirected to another location using an APP HOLD, APP HOLDMETA, APP HOLDDATA, FILEDEF, or DYNAM command, it is created in the temporary application area of the agent and disappears after the agent is released.
For example, on z/OS if DYNAM allocation for HOLDMAST or HOLDACC is present, the metadata files are created in the corresponding PDSs (for example, for a CREATE SYNONYM or TABLE FILE file with HOLD).
For related information, see Output Redirection Commands.
How to: |
Once your path is set, you can locate Master Files and procedures using the WHENCE command.
You can allocate existing data files using the following methods:
It is recommended that you use only one method for each allocation.
How to: |
For a newly created data file, the location is determined as follows:
The request that caused the file to be created determines the file DCB parameters, such as record length, record format, and so on.
For related information, see Output Redirection Commands.
The following table contains sample allocations by JCL.
VSAM |
//VSAM01 DD DISP=SHR, DSN=qualif.DATA.VSAM This type of allocation requires the szero = y parameter in the edaserve.cfg file to support sharing of BufferPool Zero. |
Fixed |
//FIX01 DD DISP=SHR,DSN=qualif.FIXED.DATA |
PDS |
//MASTER DD DISP=SHR,DSN=qualif.MASTER.DATA |
FOCUS |
//CAR DD DISP=SHR,DSN=qualif.CAR.FOCUS |
The following table contains samples of the DYNAM command.
VSAM |
DYNAM ALLOC FILE QVASM DA qualif.QVSAM.VSAM SHR REUSE |
Fixed |
DYNAM ALLOC FILE FILE1 DA qualif.FILE1.DATA SHR REUSE |
PDS |
DYNAM ALLOC FILE MASTER DA qualif.MASTER.DATA SHR REUSE |
FOCUS |
DYNAM ALLOC FILE CAR DA qualif.CAR.FOCUS SHR REU |
FI filedes DISK app/[appa.../]physfile.ftm
where:
Is a file designation.
Is an application name. It can be a nested application name.
Is a physical file located in the application.
FI filedes DISK "//'NATIVE.MVS.DATASET'"
where:
Is a file designation.
Is a Native MVS data set. It can contain any number of qualifiers, up to 44 characters long.
The USE command supports renaming of Master Files and concatenation of data sets. The USE command is the only mechanism for accessing files on the sink machine.
Renaming a Master File
USE CAR1 ON CAR END
Concatenating Master Files
USE CAR1 as CAR CAR2 as CAR END
Accessing Files on a Sink Machine
USE CAR1 AS FOCSU01 END
How to: |
If a data set name satisfies one of the following conditions, the server assumes that it is an MVS file name:
In all other cases, the name is interpreted as an HFS file name.
The following syntax is supported:
DATASET=APP1/physfile.ftm DATASET='qualif.car.data' DATASET=qualif.car.data
In addition, on z/OS, you can use the following:
GDG files | FILENAME=CARGDG,SUFFIX=FOCUS,
DATASET='qualif.CARGDG.FOCUS(0)' |
PDS members | FILENAME=CARMEMB,SUFFIX=FOCUS,
DATASET=qualif.CARPDS.DATA(CARMEMB) |
FOCUS, VSAM, Fixed | FILENAME=CAR,SUFFIX=FOCUS,
DATASET=//'qualif.CAR.FOCUS' |
WebFOCUS |