Now that your Fileshare server server1 and your enterprise server FSDEMO are both running, we will run a simple JCL jobstream to verify that new datasets are created correctly and that everything is working.
//DMFBR14 JOB 'DMFBR14',CLASS=A,MSGCLASS=A //STEP1 EXEC PGM=IEFBR14 //SYSOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //DD1 DD DSN='DMF.TEST.DSN',DISP=(MOD,DELETE) //DD2 DD DSN='DMF.TEST.DSN2',DISP=(MOD,DELETE) //*
Because you used the casstart command to start FSDEMO, you can submit the JCL from the Enterprise Developer command line. In your fsdir directory, enter:
Windows:
cassub /rFSDEMO /jc:\fsdir\iefbr14.jcl
UNIX:
cassub -rFSDEMO -j/fsdir/iefbr14.jcl
If you had started FSDEMO via ES Admin, you would have had to submit the JCL using the JES Control page in ESMAC.
The job is parsed and then waits for a batch initiator to run it.
The JCL job runs.
Select the DMFBR14 check box and click Display to display the details for the DMFBR14 jobstream, as follows:
You should see something similar to the following. Note how the Physical File field is qualified using the Fileshare server name.
You should see the joblog displayed below. The PC filenames have now been resolved to be qualified by the Fileshare server name. ($$SERVER1).
Click Back, and then click Catalog to display the JES Catalog page. Click DCB to the right of the entry for the newly created dataset DMF.TEST.DSN.
Details for the catalog entry are displayed.
You have now verified that everything is configured and working.