FAVER2 Transparency › GVFILE Applications

GVFILE Applications

The GVFILE interface also uses the FAVER2 Transparency. You will need to examine the usage of these applications. GVFILE contains the GVOPEN, GVREAD, and GVCLOSE entry points that provide access to user data stored on a FAVER export tape.

If a given application is using dynamic subroutine linkage by calling GVFILDYN before calling GVOPEN, GVREAD, and GVCLOSE, then those applications require no changes.

If a given application has GVFILE link edited into it, you will need to relink that application with the new GVFILE in order for that application to have access to the FAVER2 Transparency.

The following JCL illustrates how to relink an application to include the new GVFILE into the program:

//RELINK   JOB    '0100',SYSTEMS,CLASS=1,MSGCLASS=X
//LINK     EXEC  PGM=IEWL,
//          PARM='XREF,LIST,SIZE=(256K,48K),MAP'
//SYSUT1    DD  UNIT=VIO,SPACE=(CYL,(3,3))
//SYSPRINT  DD  SYSOUT=*
//SYSLMOD   DD  DISP=SHR,DSN=appl.link.library
//FRVOBJ    DD  DISP=SHR,DSN=CAI.ISM.LINKLIB
//SYSLIN    DD  *
//LKED.SYSIN     DD *
 REPLACE GVFILE
 INCLUDE SYSMLMOD(ProgName)
 INCLUDE FRVOBJ(GVFILE)
 ENTRY   ProgName
 NAME    ProgName(R)
//*

The FVROBJ DD statement identifies the link library where CA FAVER resides. The SYSLMOD DD identifies the application link library where your application program resides.