SOURCEFD - Sample SBX Procedure to Extract File Descriptions into Source Statements for Editing

Products

• Ramis Reporter

Issue/Introduction

This article provides a CA-Ramis SBX procedure named SOURCEFD that can be used to extract a specified file description from the RAMASTER, RAMEXTMASTER or RAMIMSMASTER dictionary.

Environment

Release:
Component: RAMIS

Resolution

The procedure creates a host system file which contains file definition statements within a free form, comma-edited MAINTAIN activity. The host file can then be used to recreate the file description or it can be edited to make changes to the file description.

SOURCEFD is provided as a sample and may be customized or modified to suit your specific needs. The source is provided in the attached file named Ramis_SourceFD.txt. Upload the text source to your mainframe using ASCII and CR/LF and compile it into your CA-Ramis user database.

Ramis_SourceFD.txt

Here are instructions for using the SOURCEFD procedure as provided:

SYNTAX: SOURCEFD filename [MSGL=msgl]

Where:

filename	The 1-12 character filename of the file description to be extracted.
msgl	Optional parameter to override CA-Ramis message level during execution. This is useful when you wish to see the results of the DEFER'ed activities. The default message level is 64.

SOURCEFD supports the extract of file descriptions for CA-Ramis database files as well as external files with the FILETYPE: QSAM, VSAM, IMS, or ISAM.

Example invocations:

SOURCEFD ramisfile
SOURCEFD QSAMfilename
SOURCEFD IMS1filename
SOURCEFD 'IMS filename'

NOTE:
As shown in the examples above, the external file FILETYPE should be provided with the FILENAME for external file descriptions. Single quotes are only needed for 'IMS' FILETYPE where the last position is a blank.

Two host files are required by the SOURCEFD procedure.

File RAMSAVEF is a temporary data set.
File RAMSAVES is the permanent data set where the MAINTAIN activity which contains the
generated file definition statements is written.

If you are running this in the CMS environment, this procedure will issue the following FILEDEFs:

SYS FILEDEF RAMSAVES CLEAR 
SYS FILEDEF RAMSAVEF CLEAR 
SYS FILEDEF RAMSAVES DISK RAMSAVES DATA A (LRECL 80 RECFM F BLKSIZE 80 
SYS FILEDEF RAMSAVEF DISK RAMSAVEF DATA A

If you are running this in the TSO environment, this procedure will issue the following ALLOCates:

SYS ALLOC F(RAMSAVES) DA(RAMSAVES) SHR  
SYS ALLOC F(RAMSAVEF) SP(1,1) TRACK REU

Data set userid.RAMSAVES must be created prior to running this procedure in TSO.
For example, RAMSAVES can be preallocated as follows:

ALLOC 
F(RAMSAVES) DA(RAMSAVES) RECFM(F) LRECL(80) SP(1,1) TRACK REU

If you are running this in the OS batch environment, you need to supply the DD statements defining RAMSAVEF and RAMSAVES.
For example:

//RAMSAVEF DD DSN=&&RAMSAVEF,DISP=(NEW,PASS),UNIT=SYSDA, 
//SPACE=(TRK,(1,1),RLSE) 
//RAMSAVES DD DSN=new.dataset,DISP=(NEW,PASS),UNIT=unit, 
//DCB=(LRECL=80,BLKSIZE=0,RECFM=FB),SPACE=(TRK,(1,1))

Or, create a member of an existing PDS that has been defined with the DCB attributes of RECFM=F or FB and LRECL=80...

//RAMSAVES DD 
DISP=SHR,DSN=pds.dataset(member)

If you are running this in the VSE environment, you need to supply the DLBL/EXTENTS defining RAMSAVEF and RAMSAVES.

NOTE: RAMSAVES must be defined as fixed with a record length of 80 so that it can be edited.

Sample execution:

SOURCEFD CLIENT

Results in informational messages:

Extract is complete for file description:      
CLIENT The host file RAMSAVES contains the extracted source.

Read More About It

For more information on writing, storing, and compiling SBX procedures, refer to the publication, CA-Ramis System Building Executive (SBX). For MAINTAIN, please refer to the publication, CA-Ramis Data Maintenance Facility (DMF). For TABLE and other reporting capabilities, refer to the publication, CA-Ramis Syntax Based Reporting.