|
|
|
If you do not plan to use CA‑L‑Serv to manage data sets, you can skip this section.
The Installation Verification Procedure for the File Server ensures that an application running on the same system as CA‑L‑Serv is able to access data sets managed by the File Server.
The installation of CA‑L‑Serv places installation verification JCL members HJ35IVF1 and HJ35IVF2 in the target source library CCCSJCL.
The File Server IVP uses the LDMAMS utility to perform a simple maintenance task against a managed data set.
Note: You may choose to back up one of your client product data sets rather than the VSAMTEST file used in this procedure.
To verify the file server installation
Customize and run job HJ35IVF1 that the installation copied into the CCCSJCL data set. This job will allocate and initialize the CAI.VSAMTEST VSAM data set as well as a sequential work file.
//HJ35IVF1 JOB (JOBACCNT) (1)
//IEFBR14 EXEC PGM=IEFBR14 (2)
//BACKUP DD DISP=(,CATLG,DELETE),DSN=CAI.VSAMTEST.BACKUP,(3)
// VOL=SER=XXXXXX,UNIT=SYSDA, (4)
// DCB=(LRECL=80,BLKSIZE=3120,RECFM=FB),
// SPACE=(3120,(1,1))
//*
//DEFCL EXEC PGM=IDCAMS (5)
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
DEFINE CLUSTER ( ‑
NAME (CAI.VSAMTEST) ‑ (6)
VOLUMES (XXXXXX) ‑
TRACKS (1 0) ‑ (7)
RECORDSIZE (80 80) ‑ (8)
KEYS (10 00) ‑ (9)
FREESPACE (10 10) ‑
SHR (2 3) ‑
REUSE ‑ (10)
INDEXED ‑
) ‑
DATA ( ‑
NAME (CAI.VSAMTEST.DATA) ‑ (6)
CISZ (8192) ‑
) ‑
INDEX ( ‑
NAME (CAI.VSAMTEST.INDEX) ‑ (6)
CISZ (2048) ‑
)
//*
//REPRO EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//SYSIN DD *
REPRO INFILE(INFILE) ODS(CAI.VSAMTEST) (11)
//INFILE DD *
0000000000 (12)
0000000001
0000000002
(etc..)
Footnotes:
(1) Provide a valid job statement.
(2) Allocate a work file.
(3) Provide a valid dsname for work file.
(4) Provide a valid volser and unit name.
(5) Allocate and initialize VSAM test file.
(6) Provide a valid dsname and volser.
(7) Space allocation.
(8) Eighty‑byte records.
(9) The key field is ten bytes long and starts at offset +0.
(10) Specify REUSE if you wish to perform other LDMAMS functions such as restores or compress.
(11) Initialize the VSAMTEST file.
(12) Provide several initialization records, making sure there are no duplicate keys and that they are in sequence.
If you choose to back up a pre‑existing data set, you can skip most of this step.
Verify that your startup deck contains an ATTACH FILESERVER statement and start CA‑L‑Serv. You can issue the following command to verify that the file server has successfully initialized:
DISPLAY TASK(FILESERVER) ALL
To place your test VSAM data set under the management of CA‑L‑Serv, issue the following command from a z/OS console:
ADDFILE ddname test.file.dsname
Customize the following JCL to meet the requirements of your data center:
//HJ35IVF2 JOB (JOBACCNT) (1) //MAMS0000 EXEC PGM=LDMAMS //STEPLIB DD DISP=SHR,DSN=CAI.CCCSLOAD (2) //BACKUP DD DISP=SHR,DSN=VSAMTEST.BACKUP (3) //SSN$xxxx DD DUMMY (4) //SYSPRINT DD SYSOUT=XA //SYSIN DD * REPRO INFILE(VSAMTEST) OUTFILE(BACKUP) (5)
Footnotes:
(1) Provide a valid job statement.
(2) Change to the CA‑L‑Serv target library.
(3) Indicate the dsname of your test sequential data set.
(4) Replace xxxx with the z/OS subsystem name you specified in your CA‑L‑Serv start procedure.
(5) The syntax is similar to the IBM IDCAMS statement.
Note: Do not allocate the VSAM file in the LDMAMS job step. This is unnecessary and would cause the job to fail.
You should see the following messages:
REPRO INFILE(VSAMTEST) OUTFILE(BACKUP)
LDM0810I nn records copied from VSAMTEST to BACKUP - REPRO
operation complete
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |