Accessing Metadata and Procedures

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.


Top of page

x
Search Rules

Unless a file name is fully qualified with the application name, the search sequence is:

  1. Current directory of the agent, which is edatemp/tsnnnnn.
  2. Applications set using APP HOLDMETA for metadata files, and APP HOLDDATA for hold data files.
  3. Applications set in APP PATH (including MVSAPP for z/OS).
  4. The baseapp application.
  5. The EDAHOME/catalog.
  6. For stored procedures only: if the file is not found, the server checks to see if the file was allocated with a FILEDEF or DYNAM command, and if so, tries to execute it.


Example: Search Paths

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.


Top of page

x
Creation Rules for Procedure Files

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.


Top of page

x
Locating Master Files and Procedures

How to:

Once your path is set, you can locate Master Files and procedures using the WHENCE command.



x
Syntax: How to Locate Master Files and Procedures

To locate a Master File or procedure, issue the following command

WHENCE filename
filetype

where:

filename

Is the name of the file you are trying to locate.

filetype

Is the type of file you are trying to locate.


Top of page

x
Accessing Existing Data Files

You can allocate existing data files using the following methods:

It is recommended that you use only one method for each allocation.


Top of page

x
Creation Rules for Data Files

How to:

For a newly created data file, the location is determined as follows:

  1. An application set by APP HOLDDATA applies to all HOLD files.
  2. For FILEDEF command, one for each data file.
  3. For z/OS, native operating system allocations when supported.

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.



Example: Sample Allocations by JCL

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


Example: Samples DYNAM Commands

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


x
Syntax: How to Issue a FILEDEF Command
FI filedes DISK app/[appa.../]physfile.ftm

where:

filedes

Is a file designation.

app/[appa...]

Is an application name. It can be a nested application name.

physfile.ftm

Is a physical file located in the application.



x
Syntax: How to Issue a FILEDEF Command for a Native MVS Data Set
FI filedes DISK "//'NATIVE.MVS.DATASET'"

where:

filedes

Is a file designation.

NATIVE.MVS.DATASET

Is a Native MVS data set. It can contain any number of qualifiers, up to 44 characters long.



Example: Sample USE Commands

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

Top of page

x
Data Set Names

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.



x
Syntax: How to Define a Data Set

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'

iWay Software