Child Care and Development Fund
Technical Bulletin #6r
CONNECT:Direct
Procedures for Submitting ACF-801 Data Files
(also in Word and
PDF)
REVISED:
March 2004
I. Introduction
The purpose of this Bulletin is to provide State child care database centers with Instructions to establish the procedures necessary to electronically transmit the ACF-801 data files using CONNECT:Direct. The data file is transmitted from the States to the Administration for Children and Families (ACF) Child Care Bureau's (CCB) Child Care Bureau Information System (CCBIS).[1] The most secure method of electronic data transmission is through CONNECT:Direct (C:D), established by the Social Security Administration (SSA). SSA uses C:D for data transfer within its secure network of State and Federal data centers. This Bulletin gives step-by-step instructions for using C:D to transfer State ACF-801 child care data files to CCBIS. The CCB's Child Care Automation Resource Center (CCARC) staff are available to provide assistance to you as you prepare for electronic submission of your data files using C:D. CCARC also will establish the User Name and Password that you will need for your data transmission (see CCARC contact information on the following page).
II. CONNECT:Direct Instructions
Step 1: Contact the State's Computer Center
First, contact the State computer center from where the data file will be transmitted. Inform them that you need information and assistance with transmitting a data file, using CONNECT: Direct, to a Federal computer center located at the National Institutes of Health (NIH) in Maryland. It is important to know who will be transmitting the ACF-801 data files and who knows how to set up the connection to NIH. Work with this point-of-contact to carry out the remaining steps in the CONNECT:Direct procedures.
To obtain the User ID and Password required to transmit the data file, or other information/assistance, contact CCARC:
Child Care Automation Resource Center (CCARC)
2600 Tower Oaks Boulevard, Suite 600
Rockville, MD 20852
1-877-249-9117
Fax: (301) 692-0700
ccarc@childcaredata.org
Step 2: Complete and Submit the Registration Form
If your State is not already registered, complete the registration form (Appendix I) and fax or e-mail it to CCARC. The point-of-contact in your State should help you complete the form. This form provides the information necessary for establishing a two-way C:D connection. Upon receipt of your form, CCARC staff will establish your User Name and Password and contact you to schedule a test.
Step 3: Write the JCL for C:D File Transmission
Create a process for sending data files to CCBIS. Write the Job Control Language (JCL) necessary to create the data transmission process. Appendix II provides a sample of JCL that you can use to create your transmittal process.
You must use the following dataset naming convention for the data file in order for it to be properly identified and processed. If you do not follow this exact naming convention, CCBIS will not be able to receive your ACF-801 data file:
VVG1IWI.PCCIS.NDM.xx.HUB.Yyyyy.Dmmdd.Thhmm
where xx is the two-letter postal code abbreviation for your State. yyyy, mmdd and hhmm respectively, are the four digit year, the two digit month and day, and the military time (based on a 24 hour clock) of the date of transmission.
For example, if you are submitting a data file for Alabama's ACF-801 data on July 15, 1998 at 1:15 pm then the dataset name should be:
VVG1IWI.PCCIS.NDM.AL.HUB.Y1998.D0715.T1315
Step 4: Create Effective Information Flow Procedures
It is important to create effective procedures between CCBIS, the State ACF-801 child care data center, and the State C:D site, especially when the location of the C:D site is different from that of the child care data center, to coordinate the transmission of the data file and the receipt of the report files.
States are encouraged to develop the following:
- A procedure for transmitting the ACF-801 data file to the State C:D site.
- A procedure for receiving report files back from the State C:D site.
These two procedures ensure that State child care data files are sent to the appropriate individual at the State C:D site for transmittal to CCBIS. These procedures also ensure that the CCBIS data assessment report files sent back to the State C:D site are forwarded to the appropriate person at the State child care data center who is responsible for the ACF-801 data. This is essential because receipt of the report files is proof that the ACF-801 data was received and processed by CCBIS.
The summary report files sent to States after the data has been submitted, received, and processed by CCBIS also serve as an important tool for assessing the quality of your data. Technical Bulletin # 9: Using the ACF-801 Data Assessment Reports, provides guidance on the use of these reports.
Examples of what States have done internally to exchange information include using a File Transfer Protocol (FTP) and sending cartridges and tapes back and forth between the computer center/site and the program office.
Step 5: Perform the C:D Data Transmission Link and Loop Test
You must perform two separate tests on your data transmission process before you can transmit the first actual data.
Test C:D data transmission link: The first test verifies that there is a data transmission link between the State C:D site and CCBIS. Transmit your test data file from your State C:D site to CCBIS. Once CCBIS receives your test data file, it transmits a test report file back to your State C:D site. The purpose of the test report is to acknowledge that the data file has been transmitted successfully. This test establishes that both sites are linked for file transmission.
Test C:D data transmission loop: The second test is called a "loop test" because it ensures that all aspects of the data transmission links between sites are working properly. Inform your Technical Assistance Liaison at the CCARC when you are ready to perform the loop test. Once the test date is established, start the test by extracting ACF-801 data from your database, creating a data file,[2] and then transmitting it to your State C:D site. That site, in turn, transmits the data to CCBIS, where the data is analyzed and processed. Next, CCBIS transmits report files to your State C:D site, that then are transmitted to the child care data collection center which originally created and sent the data file.
NOTE: Use the following dataset name for the test data file:
VVG11WI.PCCIS.NDM.xx.HUB.Tyyyy.Dyymm.Thhmm
Notice that there is a "T" instead of a "Y" where you would name the year. This indicates that this is a data file to test the connection between the State's C:D site and CCBIS and should not be processed.
Ask your contacts for the names of those who can verify the test results. In addition, you may be able to use the C:D utility, Select Statistics, to verify if the transmission was successful. Check with your State's C:D site to determine if this utility is available. Appendix III has more information about using Select Statistics.
Step 6: Transmit the Actual ACF-801 Data File
The final step is transmitting the actual ACF-801 data file based on your State's submission schedule.[3] When CCBIS receives your child care data file, it checks for file formatting and data quality. Upon receipt of your actual data, CCBIS will automatically generate two reports. The first report is the Summary Data Assessment Report. The second report is the Detail Data Assessment Report. Appendix III provides additional information about transmittal of data file and validation reports.
III. Conclusion
Transmitting the ACF-801 data file from the State C:D site to the CCBIS site takes several steps and coordination with other parties. Make sure you have the correct point-of-contacts to keep the flow of communication between the State's Child care program office, State's C:D site/data center, and the CCARC. It is important to understand what is required to establish the connection for the data and report files transmission.
This document provides step-by-step instructions for transmitting the State's ACF-801 child care data files via C:D. However, as we all know, sometimes data file transmission does not go as planned. For that reason, we invite you, or any member of your transmission team, to contact the C:D specialists at the CCARC for further assistance.
Appendix I
ACF Hub CONNECT:Direct Registration Form
______________________________________________________________________________
Items 1-4 to be filled out by State contact for ACF-801 data (See #3 below):
1. DATE: _____/_____/_______
2. STATE: ____________________________
3. STATE CONTACT: __________________________ TELEPHONE NUMBER ( )_________
4. STATE APPLICATION CONTACT:______________TELEPHONE NUMBER ( )_________
Items 5-12 to be filled out by a CONNECT:Direct contact:
|
5. STATE C:D CONTACT:_____________________ TELEPHONE: ( ) ______ -___________ 6. STATE HUB C:D NODE ID ______________________ 7. PLATFORM: MVS __ UNIX __ 8. STATE VTAM CONTACT:_____________________ TELEPHONE: ( ) ______ -___________ 9. STATE VTAM NETID: ________________ 10. STATE VTAM APPLID: ___________________ 11. Does your State require SNODEID / Password: YES_____ NO ______ 12. Point of entry security: YES _____ NO ____ |
ACF TRANSFER TO THE STATE
Item 13 to be filled out by State application contact and C:D
contact:
|
13. DSN FROM ACF TO STATE: |
|
Summary Data Assessment Report: |
|
Detail Data Assessment Report: |
NIH C:D NODE IDENTIFIERS
|
VTAM NETID: NIH VTAM APPLID: NIH4NDM C:D NODE ID: NIH.STD.NDM |
FOR ACF USE ONLY
ACF CONTACT ___________________________ REC'D DATE ____/____/____
PLEASE FAX OR E-Mail COMPLETED FORM TO THE CCARC
INSTRUCTIONS FOR COMPLETING ACF CONNECT:DIRECT REGISTRATION FORM
Items 1-4 to be filled out by State contact for ACF-801 data (See #3 below):
1. Date: Date the form is prepared.
2. State: Name of the State requesting C:D connection to NIH.
3. State Contact and telephone number: Primary State Child
Care person who has program/policy responsibility for creating and
submitting ACF-801 data. (We will contact this person if there is
a problem with the format and contents of the data.)
4. State Application Contact and telephone number: State person
who is responsible for creating C:D Process and electronically submitting
the data file from State C:D site to TITAN. (We will contact this
person if there is a problem with the file transmission.)
Items 5-12 to be filled out by CONNECT:Direct contact:
5. State C:D Contact and telephone number: State person responsible
for maintaining/setting up C:D software. (We will contact this person
if there is a C:D problem such as an incorrect Node id.)
6. State HUB C:D Node id: State's HUB CONNECT:Direct Node id.
7. Platform: Place an "X" for the appropriate platform where
C:D is running
8. State VTAM Contact and telephone number State person responsible
for maintaining/updating VTAM network definitions. (We will contact
this person if there is a network problem.)
9. State VTAM NETID: State VTAM network id.
10. State VTAM APPLID: State VTAM application id.
11. State SNODEID: Check Yes or No. If a State requires a SNODEID/Password,
we will contact you to get the information.
12. State point of entry security: Check Yes or No if point
of entry security is set-up at the State's computer system.
Item 13 to be filled out by State application contact and C:D contact:
13. DSN (filenames) for Report Files Transmitted to the State: Specify the filenames for the two report files transmitted to the State. We suggest that the report files be created as a Generation Data Group (GDG) or have a year, date and time stamp as final parameters (.Yyyyy.Dmmdd.Thhmm). The State needs to provide us with the DISP, UNIT, and VOL=SER parameters.
Appendix II
Sample JCL
______________________________________________________________________________
There are two options for electronically transmitting the data file to CCBIS. States may elect the option they would like to use:
- Option 1: Create your own C:D SUBMIT and COPY process. Use this option if you wish to customize the C:D process to automate tasks beyond file transmission. For example, if you want to send a notification that the transmission process has been completed, you can automate this task by coding it in a process.
- Option 2: Use an existing standard C:D COPY process provided with the software.
Following are descriptions for implementing either option:
OPTION 1
You may use the following sample to create your own JCL batch job and C:D SUBMIT and COPY process for the ACF-801 data file transmission to CCBIS. Please note that the information specified in the following JCL sample may require modifications to conform to your own data center environment.
//jobname JOB--Enter the required job statement parameters
for the State installation.
//* (Connect:Direct)--Transmit a state file directly to CCBIS
//DMBATCH EXEC PGM=DMBATCH,REGION=1M,PARM=(YYSLYNN)
//STEPLIB DD DISP=SHR,DSN=SYS3.NDM.COMMON.LOADLIB
//DMNETMAP DD DISP=SHR,DSN=SYS3.NDM.COMMON.NETMAP
//DMPUBLIB DD DISP=SHR,DSN=SYS3.NDM.COMMON.PROCESS.LIB
//DMMSGFIL DD DISP=SHR,DSN=SYS3.NDM.COMMON.MSG
//DMPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
SIGNON
SUBMIT PROC=PROC01
-
NOTIFY=See below for description of appropriate value
-
PNODE=See below for description of appropriate value
-
SNODE=NIH.NDM
-
&DSN1=See below for description of appropriate value
-
&DSN2= VVG1IWI.PCCIS.NDM.xx.HUB.Yyyyy.Dmmdd.Thhmm -
&NODE=PNODE
-
&DISP1=NEW
-
&DISP2=CATLG
-
&UNIT=FILE
SIGNOFF
/*
//
Description of appropriate values:
| NOTIFY = | ______ | Specify the userid to notify when the process is executed |
| PNODE = | ______ | Specify your State's C:D node id |
| DSN1 = | ______ | Specify the State's ACF-801 dataset name being transmitted |
| DSN2 = | VVG1IWI.PCCIS.NDM.xx.HUB.Yyyyy.Dmmdd.Thhmm This is a required dataset naming convention, where xx is the State's two-letter postal code abbreviation, and yyyy is the four-digit year, mm is the month, dd is the day, and hhmm is the time (in military format - e.g. 2359 represent 11:59 pm.) the file is submitted. | |
The following code is a C:D COPY process, that is invoked by the C:D SUBMIT command in the above JCL batch job. Please note that this process must reside in the Partitioned Data Set (PDS) library referenced by the above DMPUBLIB DD statement. In addition, its member name must be the same as the member identified in the above C:D Submit command. For example, the following COPY process would be named PROC01 to correspond with the name used in the above SUBMIT PROC statement. However, if you had assigned a different name in the SUBMIT PROC statement, the COPY process would be assigned the same name.
SEND801 PROCESS SNODE=&SNODE PNODE=&PNODESNODEID-(userid,password)
STEP 1 COPY FROM(PNODE DSN=&DSN1 -
DISP=SHR) -
COMPRESS -
TO(SNODE DSN=&DSN2 -
DISP=(&DISP1,&DISP2) -
UNIT=&UNIT)
OPTION 2
The following sample uses a COPY01 process that is a standard (generic) C:D copy process that should reside in the DMPUBLIB library. You may use the following sample to create your C:D SUBMIT process for the ACF-801 data file transmission to CCBIS. Please note that the information specified in the following JCL sample may require modifications to conform to your own data center environment.
//jobname JOB--Enter the required job statement parameters
for the State installation.
//*
//DMBATCH EXEC PGM=DMBATCH,REGION=1M,PARM=(YYSLYNN)
//STEPLIB DD DISP=SHR,DSN=SYS3.NDM.COMMON.LOADLIB
//DMNETMAP DD DISP=SHR,DSN=SYS3.NDM.COMMON.NETMAP
//DMPUBLIB DD DISP=SHR,DSN=SYS3.NDM.COMMON.PROCESS.LIB
//DMMSGFIL DD DISP=SHR,DSN=SYS3.NDM.COMMON.MSG
//DMPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
SIGNON
SUBMIT PROC=COPY01
-
NOTIFY=See below for description of appropriate value
-
PNODE=See below for description of appropriate value
-
SNODE=NIH.NDM
-
&DSN1= See below for description of appropriate value
-
&DSN2=VVG1IWI.PCCIS.NDM.xx.HUB.Yyyyy.Dmmdd.Thhmm
-
&NODE=PNODE
-
&DISP1=NEW
-
&DISP2=CATLG
-
&UNIT=FILE
-
&COMPRESS=COMPRESS
SIGNOFF
/*
//
Description of appropriate values:
NOTIFY = ______ Specify the userid to notify
when the process is executed
PNODE = _______ Specify your State's C:D node
id
SNODEID=(userid,password)
DSN1 = ________ Specify the State's
ACF-801 dataset name being transmitted.
DSN2 = VVG1IWI.PCCIS.NDM.xx.HUB.Yyyyy.Dmmdd.Thhmm
This is a required dataset naming convention, where xx is the
State's two-letter postal code abbreviation, and yyyy is the
four-digit year, mm is the month, dd is the day, and
hhmm is the time (in military format - e.g. 2359 represent
11:59 p.m.) the file is transmtted.
Appendix III
Data and Report Files Transmission and Transmission Validation
Process
______________________________________________________________________________
I. Introduction
There are two methods of transmitting files between the State's C:D site and CCBIS. States can use either of the two transmission methods for sending data files and receiving report files:
- an online Interactive User Interface (IUI)
- a batch job process
Following is a detailed description of the IUI and batch job process for the data file transmission and the transmission validation process, and the validation process for the report files transmitted from CCBIS. While the two processes are similar, follow the instructions for the method your State will use.
II. The IUI Data Transmission and Validation Process
Transmit Data: The IUI data transmission process includes steps to "submit" and "copy" the data. To "submit" the data, enter an online IUI submit command. This submit command executes a C:D submit process command. This is a request to C:D to execute a process that resides in the State's C:D process library. Following a successful submit request, C:D executes a process that resides in the State's C:D process library. This process contains a C:D copy statement that instructs the computer to copy the data file from the State C:D site to CCBIS.
Validate Transmission: After running a successful IUI transmission using the submit command, the system displays the message: "Submit process successful." If an error message tells you the transmission is unsuccessful, debug the process so it enables a successful transmission. To determine if the copy command was successful, do the following to access the Select Statistics menu and validate that the data was copied:
- From your system, access the CONNECT:Direct Primary Options Menu (Screen A-1). Select "SS" ("View Statistics for a Completed Process") from this menu:
|
Node.name CONNECT:Direct
for MVS PRIMARY OPTIONS MENU |
Screen A-1: Primary Options Menu
- This will display the Select Statistics screen (Screen A-2):
|
Node.name
SELECT STATISTICS PROCESS NUMBERS: CMD:
DIS CONDITION CODE:==> __________ EXCLUDE ( MEMBER RECS ==> M WTO RECS ==> N WTO RECS ==> N ) CHANGE EXTENDED OPTS: ==> N CMD: S . SUMMARY TABLE D . DISPLAY REPORT P .PRINT REPORT |
Screen A-2. IUI Facility Select Statistics
- Enter the following values in the Select Statistics screen to display the Statistics Summary:
- In the CMD field enter "S".
- In the PROCESS NAMES field enter the process name for the
C:D process that resides in the State's C:D process library.
The example for JCL Option 1 has a process name of "SEND801" and
that for JCL Option 2 has a process name of "COPY01". (See
Appendix III.)
- In the START DATE field enter the date of the transmission.
Enter "TODAY" for the current date, or enter a specific date using
a date format of mm/dd/yyyy. C:D retrieves statistics for
processes with the specified process name and date.
- Press enter.
- Screen A-3, below, is a sample of a Statistics Summary:
|
---------------------------STATISTICS SUMMARY-------
ROW 1 TO 3 OF 3 FUNCTION PNAME
PNUMBER SUBMITTER
NODE==OTHER NODE---- SUB-CMD SEND801
8326
NDM.STATE NIH.NDM |
Screen A-3. IUI Facility Select Statistics Summary
- C:D displays a three-line summary of the statistics records for each C:D process function. The first and second lines of each entry identify a process by function (FUNCTION), process name (PNAME) and number (PNUMBER), submitter or other node, and userid. The third line of each entry is the message id return code (RTNCD), and the ending date and time (END DATE/TIME) of that process. Each C:D process function is successful if the third line has a RTNCD of "00000000". The C:D process function is unsuccessful if the third line has a non-zero RTNCD. An asterisk appears to the left of an entry if a non-zero RTNCD is present.
- There should be an entry for the SUBMIT process (see"SUB-CMD" lines of Screen A-3). If a RTNCD of "00000000" is present, the process was successful. If a non-zero RTNCD is present, the process is unsuccessful. Enter "M" next to the process name to display the specific error message.
- There should be an entry for the COPY process (see "COPY" lines of Screen A-3), which contains a C:D copy statement to copy the data file from the State to CCBIS. If a RTNCD of "00000000" is present, the process is successful. Entering "S" next to the process name displays the detail statistics, such as the compression ratio of the transfer. If a non-zero RTNCD is present, the process is unsuccessful. Enter "M" next to the process name to display the specific error message.
Validation of Report Files Transmission
If the data file transmission was successful, CCBIS will process the data file and generate two report files. A periodic "sweep" process initiates a C:D process at CCBIS which copies the reports to the State's C:D site. The process name is: CCISTOxx (where xx represents the State postal code abbreviation). When this process is executed, C:D generates statistic log records that indicate whether the reports are copied from CCBIS to the State site successfully. Please note that C:D generates a copy of the statistics log records on the State's site as well as on the CCBIS site.
- From your system, access the CONNECT:Direct Primary Options Menu (Screen A-1). Select "SS" ("View Statistics for a Completed Process") from this menu.
- This displays the Select Statistics screen (see Screen A-2). Enter the following values to display a three line summary of the statistics records:
- In the CMD field enter "S".
- In the PROCESS NAMES field enter "CCISTOxx", where
xx represents the State postal code abbreviation. This
is the C:D process that copies the reports to the State's C:D system.
- In the START DATE field enter the date of the attempted
report transfer. (The CD site will submit reports within 24
hours of data arriving.) Enter "TODAY" for the current date,
or enter a specific date using a date format of mm/dd/yyyy.
C:D retrieves statistics for all the processes run on or after this
date.
- Press enter.
- C:D displays a three-line summary of the statistics records for each C:D process function. (See Screen A-3.) The first and second lines of each entry identify a process by function, process name and number, submitter or other node, and userid. The third line of each entry is the message id RTNCD, and the ending date and time of that process. Each C:D process function is successful if the third line has a RTNCD of "00000000". The C:D process function is unsuccessful if the third line has a non-zero RTNCD. An asterisk appears to the left of an entry if a non-zero RTNCD is present.
- There should be an entry for each report file sent to the State. (See Screen A-3). Each entry represents the process execution that contains a C:D copy statement to copy the report file from the CCBIS site at NIH to the State site. If a RTNCD of "00000000" is present, the process is successful. You may enter "S" next to the process to display the detail statistics of the transfer, such as the compression ratio. If a non-zero RTNCD is present, the process is not successful. Enter "M" next to the process name to display the specific error message.
III. THE BATCH JOB TRANSMISSION AND VALIDATION PROCESS
Transmit Data: The batch data transmission process includes steps to "submit" and "copy" the data. To "submit" the data, enter a submit command. This submit command executes a C:D submit process command. This is a request to C:D to execute a process that resides in the State's C:D process library. Following a successful submit request, C:D executes a process that resides in the State's C:D process library. This process contains a C:D copy statement which instructs the computer to copy the data file from the State C:D site to CCBIS.
Validate Transmission: After running a successful batch transmission using the submit command, the MVS generates the completion code (Comp Code) of "00000000." If there is any other value, the transmission is unsuccessful. To determine if the copy command was successful, do the following to view the Select Statistics screen and validate that the data was copied:
- View the statistics records in batch mode by running a batch submit, as you did before. (See JCL batch job in Option 1 or Option 2.) The following is an example of a JCL process to run a C:D select statistics job. Please note that the information specified in the following JCL sample may require modifications to conform to your own data center environment.
//jobname JOB--Enter the required job statement parameters
for the State installation.
//* (Connect:Direct)--View statistics records for data transmission
//DMBATCH EXEC PGM=DMBATCH,REGION=1M,PARM=(YYSLYNN)
//STEPLIB DD DISP=SHR,DSN=SYS3.NDM.COMMON.LOADLIB
//DMNETMAP DD DISP=SHR,DSN=SYS3.NDM.COMMON.NETMAP
//DMPUBLIB DD DISP=SHR,DSN=SYS3.NDM.COMMON.PROCESS.LIB
//DMMSGFIL DD DISP=SHR,DSN=SYS3.NDM.COMMON.MSG
//DMPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
SIGNON
SEL STAT WHERE ( PNAME=state_process_name
-
STARTT=(TODAY))
SIGNOFF
/*
//
- In the state_ process_name field, enter the name shown in the State's C:D process library. The example for JCL Option 1 has a process name of "SEND801," and that for JCL Option 2 has a process name of "COPY01".
- The STARTT represents the date you attempt to transfer the data file. Enter a specific date by using the "mm/dd/yyyy format" or you can substitute "TODAY" for the current date. C:D retrieves statistics for processes with the specified name run on or after this date.
- The output for a batch job is different from the output for an IUI process. You still receive detailed statistics for each process, which is successful if there is a Comp Code of "00000000," and unsuccessful if there is a non-zero Comp Code and an error message.
- There should be an entry for the C:D SUBMIT statement. A Comp Code of "00000000" indicates the process is successful, and a non-zero Comp Code, unsuccessful (Screen A-4).
|
|||||||||
Screen A-4. Batch Job Select Statistics for the Submit Command
- There should also be an entry for the C:D COPY statement, a command to copy the data file from the State to CCBIS. A Comp Code of "00000000" indicates the process is successful, and a non-zero Comp Code indicates it is unsuccessful. (Screen A-5.)
|
||||||||||||||||||||
Screen A-5. Batch Job Select Statistics for the Copy Command
Validation of Report Files Transmission
If transmission was successful and the data file was successfully processed, reports are generated by CCBIS and returned to the State via C:D within 24 hours of receiving the initial data file. A periodic "sweep" process submits a C:D process on the CCBIS system to copy the reports to the State's system. The process name is: CCISTOxx (where xx represents the State postal code abbreviation). When this process is executed, C:D generates statistic log records that indicate whether the reports are copied from CCBIS to the State successfully. Use the Select Statistics command to retrieve and examine the statistics records generated by C:D.
- To view the statistics records in batch mode you must run a batch submit, as you did before. (See JCL batch job in Option 1 or Option 2.) Substitute the following control cards and replace the fields in italics with the following values. Please note that the information specified in the following JCL sample may require modifications to conform to your own data center environment.
//jobname JOB--Enter the required job statement parameters for the State installation.
//* (Connect:Direct)--View statistics records for report transmission
//DMBATCH EXEC PGM=DMBATCH,REGION=1M,PARM=(YYSLYNN)
//STEPLIB DD DISP=SHR,DSN=SYS3.NDM.COMMON.LOADLIB
//DMNETMAP DD DISP=SHR,DSN=SYS3.NDM.COMMON.NETMAP
//DMPUBLIB DD DISP=SHR,DSN=SYS3.NDM.COMMON.PROCESS.LIB
//DMMSGFIL DD DISP=SHR,DSN=SYS3.NDM.COMMON.MSG
//DMPRINT DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
SIGNON
SEL STAT WHERE (PNAME =
CCISTOxx -
STARTT = (TODAY ))
SIGNOFF
- CCISTOxx: where xx represents the State
postal code abbreviation. This is the process on the C:D site
that copies the report files to the State's C:D site.
- The STARTT represents the date the system attempts to transfer
the report file. (Report files are transmitted within 24 hours of
data arriving.) Enter a specific date by using the "mm/dd/yyyy
format" or you can substitute "TODAY" for the current date.
C:D retrieves statistics for processes with the specified name run
on or after this date.
- The output is different than that for the IUI process. However,
you still receive detail statistics for each C:D process.
Each function is successful if it has a Comp Code of "00000000"
and unsuccessful if it has a non-zero Comp Code and an error message.
- There should be an entry for each report file sent to the State. Each entry represents a C:D copy statement from CCBIS to the State. If a copy code of "00000000" is present, the process is successful. If a non-zero Comp Code is present, the process is unsuccessful.
[1] The CCBIS is located at the National Institute
of Health (NIH) computer center in Bethesda, MD. State data
files first are transmitted to the NIH TITAN mainframe and then moved
to the DEC Alpha Unix Server where they are processed.
[2] For the test, States may choose to send
either the entire first submission or a portion of the records in
the first submission. In either case, the loop test submission
must be a properly formatted CCBIS file. Technical Bulletin
#4 describes ACF-801 Case-level File Format.
[3] States are given the option to submit
data on a monthly or quarterly schedule. Once started, a State may
not change their submission schedule until the beginning of the next
Federal fiscal year.
