The initiation procedure creates eight sets of job streams which you can edit and save under the logon ID you will be assigned by FIRN. Appendix L contains a sample of the generated Job Control Language (JCL). In this appendix ACCT represents your 6-character NWRTSO logon ID provided by FIRN (e.g. FNDX03). DSNPRFX represents your default dataset name prefix which is generated from your logon ID by inserting a period between characters 2 and 3 (e.g. FN.DX03). All editing is done using the facilities of ISPF under TSO. After a dataset has been edited and saved you can submit it for execution via the System's menu screens or through any other process by which batch jobs may be submitted at NWRDC.
Since you already have an account for student record processing at NWRDC, file transfer is easy. You must modify your ACF2 dataset rules to grant the FIRN-provided logon ID read access to the datasets (under your existing account) for the request and response records you wish to submit to the System. You must grant read/write/allocate access to the datasets containing the request and response records the System generates for you. You also need to grant read/write/allocate access to the datasets that will contain the request and response edit error records generated by programs SRTS01 and SRTS03. For example, suppose your existing logon ID at NWRDC is CBAY and you have been assigned logon ID FNDX03 by FIRN. The following permissions could be granted:
CBAY grants FNDX03 read authority on
CBAY grants FNDX03 read/write/allocate authority on
By substituting these dataset names in the appropriate JCL streams, you would then be able to generate requests and responses on your existing logon ID for pickup by the System. You would also have the System delivering requests and responses from other institutions to datasets accessible by your existing number.
--------Florida Automated System for Transferring Educational Records-------
COMMAND===>
Institution: LEON SCHOOL DISTRICT 10/01/1990
09:45
On-line Database Functions:
U - UPDATE LOCAL SITE DEFAULT VALUES
M - REVIEW MAILBOX STATUS
P - PARTICIPANT STATUS
& CONTACTS INFORMATION
Batch Execution Job Streams:
4 - POST BATCH OF REQUESTS
5 - POST BATCH OF RESPONSES
6 - RECEIVE REQUESTS Generate and Edit a New Job Stream
7 - RECEIVE RESPONSES -or- Edit Only an Existing Job
8 - OUTGOING AGING REPORT Stream -or- Submit an Existing
9 - INCOMING AGING REPORT Job Stream (G, E, or S) ==> E
10 - PARTICIPANT STATUS REPORT
11 - CONTACTS LIST REPORT
X - EXIT MENU
|
To conduct the initiation session, logon to TSO under the FIRN-provided logon ID. After a brief pause, you will be presented with a menu screen similar to the one shown in Figure V-1. This menu has eleven options, plus one more for exiting the menu. Note that when you exit this menu, you will then be presented with the ISPF Information Center Menu screen. You can exit this screen by pressing PF3 (program function key 3), and sign off by typing logoff and pressing the return key. But don't select exit at this point. Select option U, instead, to update your profile default values.
Florida Automated System for Transferring Educational Records
Update Local Site Default Values
Enter new values to update default values:
Node Name: XXXXXX Remote ID: XXXXXX
Transfer Type: XXX
Site Sending LU OR Remote NetView LU: XXXXXXXX
Site Receiving LU: XXXXXXXX
NWRDC Sending LU: XXXXXXXX NWRDC Receiving LU: XXXXXXXX
File Type: XXXX
FTP Checkpoint Restart DSN: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
FTP Load Library Name (MVS): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
FTP Checkpoint Restart VCAT (DOS): XXXXXXXXXX
'GO' to submit job, 'CAN' to cancel: XXX |
By selecting option U (type the letter U on the COMMAND line and press the return key), you will be presented with a screen resembling the one shown in Figure V-2. Eleven parameters are presented, but you only need to be concerned with the first three:
As an NWRDC Local institution, your Transfer Type will always be LCL, and your Node Name will probably be NWR. Your remote ID may already have been filled in, but if it's blank or isn't what you want it to be, change it to the proper value. Also check the File Type parameter which--if it isn't already--must be set to SAM. When you have the parameters set to the right values, type the word go on the final line of the screen and press the return key. This will update your profile. Typing the word can, on the other hand, would cancel this screen, leaving your profile unchanged.
B. Customize JCL to Send RequestsAfter typing go or can, you will again be returned to the System's main menu. You are now ready to generate your first JCL stream, the stream that will execute program SRTS01 and post a batch of requests to your addressees' mailboxes. Type the number 4 on the COMMAND line. Then type a g into the Generate/Edit/Submit field in the lower right hand corner of the screen where, in Figure V-1, it reads:
This lets the System know that you want to generate an entire new JCL stream. Had you typed an e you would have told the System that you wanted to edit a JCL stream that you had previously generated (you will select this option when, at some later date, you need to make a change to the JCL you have stored at NWRDC). Use the s option when you want to submit a previously generated and edited JCL stream to NWRDC for execution.
After typing the g, press the return key. You will then be presented with a screen resembling the one shown in Figure V-3. This screen has four parameters:
Florida Automated System for Transferring Educational Records
POST BATCH OF CURRENT REQUESTS
Enter new parameters to override your LCL defaults:
NWRDC system parameters:
Job Class: X
Job Time (Format = "(min,sec)"): XXXXXXXX(,10)
Name of input dataset to be processed:
DSN (up to 44 chars.): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Name of error file dataset to be created at NWRDC
DSN (up to 44 chars.): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
'Edit' to edit generated job stream, 'CAN' to cancel: EDIT
|
Job Class should be set to A for daytime operations or C for the lower nighttime rate. There is also class G (an even lower rate) that may be used over weekends, but this should be used sparingly since there is no guarantee that the job will execute to completion.
Ten seconds--entered as (,10)-- is the default Job Time setting. This default is sufficient to process about 1,500 requests, so you probably won't have to adjust it in the normal course of affairs.
Input Dataset Name may be up to 44 characters in length. You should set this to the name of the dataset, under your existing NWRDC logon ID, to which you granted your FIRN-provided logon ID read permission. In the example at the beginning of this section, this was CBAY.REQUESTS.ONTO.SYSTEM.
The Error File will hold copies of all request records rejected for edit errors. Its data set name may also be up to 44 characters in length. You should already have granted your FIRN-provided account read/write/allocate authority on this dataset. In the example at the beginning of this chapter, this dataset name was CBAY.REQUESTS.ONTO.SYSERRS.
EDIT ---- FN.DX03.REQUESTS.ONTO.SYSJCL --------------------- COLUMNS 001 072 COMMAND ===> SCROLL ===> CSR ****** ***************************** TOP OF DATA *************************** 00001 NOTE== JOB STREAM TO POST REQUESTS RECORDS - 06/09/89 08:54:22 00002 NOTE== LINES TO BE EDITED ARE UNIQUELY MARKED BY A LINE CODE DELIMITED 00003 NOTE== BY DOUBLE PLUS SIGNS IN THE FIRST 8 CHARACTERS (EG. ++MS.1++). 00004 NOTE== INSTRUCTIONS FOR EDITING EACH LINE ARE EMBEDDED THROUGHOUT THE 00005 NOTE== TEXT. ALL 'NOTE==' LINES AND LINE CODE MARKERS MUST BE DELETED 00006 NOTE== BEFORE SUBMITTING THE JOB STREAM OR THE JOB WILL NOT EXECUTE. 00007 NOTE== 00008 NOTE============================================ BEGIN JC SECTION ==== 00009 NOTE== LINES THAT NEED TO BE EDITED IN JC SECTION: (EXECUTED AT NWRDC) 00010 NOTE== JC.1 = NWRDC JOB CARD 1 00011 NOTE== JC.2 = NWRDC JOB CARD 2 00012 NOTE== JC.3 = NWRDC PASSWORD CARD 00013 NOTE== JC.4 = ROUTE PRINT TO LOCAL SITE 00014 NOTE== JC.5 = ROUTE PUNCH TO LOCAL SITE 00015 ++JC.1++//FNDX03SQ JOB (FNDX03),'PROGRAMMER NAME',MSGLEVEL=(0,0), 00016++JC.2++//REGION=4096K,MSGCLASS=A,TIME=(,10),CLASS=A 00017/*JOBPARMCARDS=999999,LINES=9999 00018 /*ROUTE XEQ NWR 00019 ++JC.3++/*PASSWORD NWRPSWRD PF 1=HELP 2=SPLIT 3=END 4=RETURN 5=RFIND 6=RCHANGE PF 7=UP 8=DOWN 9=SWAP 10=LEFT 11=RIGHT 12=CURSOR |
After setting all parameters, press the return key. The System, using the information provided in your profile, will create a JCL stream and write it to a dataset under your FIRN-provided account. You will then be presented with a screen similar in appearance to the one shown in Figure V-4. This is an ISPF editing screen. In the upper left hand corner is the name of the dataset being edited (the dataset which contains the JCL stream that has just been generated). This name will be in the format:
DSNPRFX.REQUESTS.ONTO.SYSJCLwhere DSNPRFX is your default dataset name prefix. ISPF is a full screen editor, with "PF" (program function) keys displayed on the lower two lines of the screen. It is similar to many mainframe editors and, if you need assistance on using it, you may press PF1 and receive on-line HELP on any of ISPF's features (pressing PF3 ends the HELP session). Figure V-4 displays a window which, at this time, is looking into the first 19 lines of the JCL stream.
Pages 2 and 3 of Appendix L contain the text of the JCL stream you have generated. The first 14 lines contain some notes on the lines you will need to edit. Note that, after all other editing is complete, you must delete any line that begins with the word NOTE.
As the instructions say, there are five lines that you must edit. These are labeled with plus signs (++) in the first 2 characters. You may edit these lines in any way that you wish, as long as you finish by removing all characters between the pair of double plus signs, and the double plus signs themselves. Suppose, for example, you want to edit the JOB card, replacing the parameter PROGRAMMER NAME with your name. Initially, this line would look like this:
++JC.1++//FNDX03SQ JOB (FNDX03,,,99,0,,,,82),'PROGRAMMER NAME',MSGLEVEL=(0,0),
Note that this is the job statement for FIRN user account FNDX03. After editing to change PROGRAMMER NAME to JANE DOE, this line would appear as follows:
//FNDX03SQ JOB (FNDX03,,,99,0,,,,82),'JANE DOE',MSGLEVEL=(0,0),
It is likely that lines JC.2, JC.4, and JC.5 will not need much editing, other than to remove the double plus line labels. Line JC.1 should be edited for naming purposes, and you must change line JC.3, replacing NWRPSWRD with your FIRN-provided NWRDC password.
This is the parameter statement for program SRTS01. The parameter, in the first column, has been set to "B", directing the program to produce both a printer report and a data file of the records rejected for having edit errors. Note (on page L-2) that the formats for the parameter statements for this and all System programs are provided as comment statements in each JCL stream you will generate. If you wanted the program to produce only the printer report, you would need to change the "B" to a "P". You would also need to change the five-line DD statement for the request error file RQSERRS to the following single line:
In most cases, you will not need to edit the rest of the JCL stream. There is one situation, however, in which you will need to make additional modifications. If you are processing more than 2,100 requests, you will need to increase the size of the four SORTWK datasets. These appear on page L-3 and have SPACE allocations set to (TRK,(3,3),RLSE). Room for 2,800 requests would be provided by changing all four SORTWK allocations to (TRK,(4,4),RLSE), another 700 can be provided by increasing SPACE to (TRK,(5,5),RLSE), etc.
When you have made all the edits you wish (remembering to delete the NOTE lines) you may exit the editor by pressing the PF3 key. The System will then present you with a screen similar to the one shown in Figure V-5. This screen presents you with two questions. In the first, you are asked whether or not you want to have the JCL you just edited saved as a disk file. The default value is to have the JCL saved.
Florida Automated System for Transferring Educational Records
Disposition of Generated JCL
Do you want to SAVE the JCL at NWRDC (DEFAULT) or do you want to
DELETE the JCL: XXXXXX
Next step - NOACTION taken (DEFAULT)
REEDIT the JCL
DOWNLOAD the JCL to your local site PUNCH queue
SUBMIT the JCL for execution: XXXXXXXX
If you requested that the JCL be DOWNLOADED, please supply
a JOB NAME: XXXXXXXX
and a PROGRAMMER NAME: XXXXXXXXXXXXXXXXXX
If you wish to modify the PRINT/PUNCH destination, please supply
a PRINT DESTINATION: XXXXXXXX
and/or a PUNCH DESTINATION: XXXXXXXX
|
The second question gives you four choices. You can:
| - | choose to return to the main menu without doing any additional operations (this is the default), |
| - | choose to return to the editor to make, potentially, more changes to the JCL stream, |
| - | have the JCL stream downloaded to your localsite's PUNCH queue and then return to the main menu, or |
| - | have the JCL stream submitted for execution,after which you would be presented with the main menu. |
This fourth choice is one you can use if you wish to use the on-line System to release your batch jobs for execution.
If you choose to have the JCL stream routed to your local PUNCH queue, you must also enter the two fields at the bottom of the screen: Job Name, and Programmer Name. You may also enter alternate PRINT and/or PUNCH remote queue designations in two fields provided at the bottom of the screen.
When you have completed filling out this screen, press the return key. The System will then perform the operations as you have directed and return you to the main menu (unless your choice was to return to the editor). You now will have created the JCL stream necessary to post a batch of request records to the System.
C. Customize JCL to Send ResponsesYou are now ready to generate the JCL stream that will execute program SRTS03 and post a batch of responses to your addressees' mailboxes. Type a 5 on the main menu's COMMAND line, and a g into the Generate/Edit/Submit field on the lower right hand corner of the screen to let the System know that you want to generate a new response-posting JCL stream. After typing the g, press the return key. You will then be presented with a screen resembling the one shown in Figure V-6. This screen has four parameters:
Job Class should be set in the same way as for request processing. The default Job Time of 10 seconds is sufficient to process about 91 transcripts (say, 9,100 response records). You may need to adjust this parameter. If you have to err, do so on the side of safety. For example, if you have 1000 transcripts to process with an average of 100 response records per transcript, that would leave program SRTS03 with 100,000 response records to process. That is about 11 times as many records than it would be safe to attempt to process with a time limit of 10 seconds, the default. Eleven times 10 gives 110 seconds, or one minute fifty seconds. It would be reasonable to round this up to a full two minutes, which would be rounded up typed as (2).
Input Dataset Name may be up to 44 characters in length. You should set this to the name of the dataset, under your existing NWRDC logon ID, to which you granted your FIRN-provided logon ID read permission. In the example at the beginning of this section, this was CBAY.RESPONSE.ONTO.SYSTEM.
Florida Automated System for Transferring Educational Records
POST BATCH OF CURRENT RESPONSES
Enter new parameters to override your LCL defaults:
NWRDC system parameters:
Job Class: X
Job Time (Format = "(min,sec)"): XXXXXXXX(,10)
Name of input dataset to be processed:
DSN (up to 44 chars.): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Name of error file dataset to be created at NWRDC
DSN (up to 44 chars.): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
'Edit' to edit generated job stream, 'CAN' to cancel: EDIT
|
The Error File, which is in Header Record format, will hold copies of the Header Records for all response records found to have edit errors. Its dataset name may also be up to 44 characters in length. You should already have granted your FIRN-provided account read/write/allocate authority on this dataset. In the example at the beginning of this chapter, this dataset name was CBAY.RESPONSE.ONTO.SYSERRS.
After setting all parameters, press the return key. The System, using the information provided in your profile, will create a JCL stream and write it to a dataset under your FIRN-provided account. You will again be presented with an ISPF editing screen similar in appearance to that shown in Figure V-4. The dataset you will be editing, this time, will be named:
where DSNPRFX is your default dataset name prefix.
Pages 4 and 5 of Appendix L contain the entire text of the JCL stream you have generated. This JCL stream is very similar to the stream for posting requests. You edit the same five lines, and there are the same NOTE lines to be deleted. The main difference is that your input will be from DD name RSPFILE, which will have been set to CBAY.RESPONSE.ONTO.SYSTEM if you typed this dataset name on the previous screen. Also, this JCL stream will execute program SRTS03; and your error file will be written to DD name RSPERRS, which will be set to CBAY.RESPONSE.ONTO.SYSERRS.
You will also need to adjust the SPACE allocations of your SORTWK datasets if relatively large numbers of response records are being processed. The default allocation(CYL,(1,1),RLSE) is sufficient for about 10,000 response records (or 200 transcripts of 50 records each). Adjusting this allocation to (CYL,(2,2),RLSE) on all four datasets doubles the number of records you can process. (CYL,(3,3),RLSE) triples capacity, etc.
This is the parameter statement for program SRTS03. The parameter, in the first column, has been set to "B", directing the program to produce both a printer report and a data file of responses found to have edit errors. If you wanted the program to produce only the printer report, you would need to change the "B" to a "P". You would also need to change the five-line DD statement for the response error file RSPERRS to the following single line:
When you have made all the edits you wish (remembering to delete the NOTE lines), exit the editor by pressing the PF3 key. The System will then present you with a screen similar to that in Figure V-5. Resolve the questions put to you by this screen in the same way you did with the request-posting JCL stream. Then press the return key. The System will perform the operations you have directed and return you to the main menu (unless your choice was to return to the editor). Now you will have created both of the JCL streams used to get records from your files to the System. The next two sections deal with the flow of records in the opposite direction.
D. Customize JCL to Receive RequestsThis time, select the RECEIVE REQUESTS option by typing a 6 on the main menu's COMMAND line. Then type a g in the Generate/ Edit/Submit field then press the return key. You will be presented with a screen that looks similar to the one shown in Figure V-7. This screen has 4 parameter fields you can fill in:
Florida Automated System for Transferring Educational Records
RECEIVE CURRENT REQUESTS
Do you want CURRENT requests or do you need to
RETRANSMIT previously received data: XXXXXXXXXX
For a retransmittal of previously transmitted requests enter dates:
mmddyyyy
BEGINNING DATE: XXXXXXXX
ENDING DATE: XXXXXXXX
To select the type of output
enter "F" for a generated file, or
enter "P" for a printed report,
or
enter "B" for both: X
PF3=Main Menu
|
The Selection Criteria field governs the type of request records that are to be retrieved by the JCL stream you are going to create. Normally, you will be retrieving those requests in your mailbox that have not yet been delivered. These are referred to as your "current" requests. Retransmission of request records (meaning, literally, the retrieval of records that already have been retrieved at least once) will be dealt with in Section F. To select your current requests, type current in the Selection Criteria field in the upper right of the screen. The next two fields, Beginning and Ending Date, are applicable only to record retransmission situations. Leave them blank.
The fourth field specifies the form in which you wish to receive the request records from the System. You may choose to receive your requests as a machine-readable file (by typing the letter f) or as a printer report in the format shown in Appendix T (by typing the letter p). You may also elect to have both of the above operations performed, by typing the letter b.
For purposes of this discussion, both a machine-readable file and a printer report will be selected. Having typed the letter b on the next to the last printed line shown in Figure V-7, you will then press the return key. Note that if you wish to cancel the entire operation and return to the main menu you may press the PF3 key.
You will now be presented with a screen similar to the one shown in Figure V-8. The usual parameters may be entered: Job Class, Job Time, and Output Dataset Name (essentially the same as Input Dataset Name, but specifies the name of the dataset you want requests written to instead of read from). You follow the same kind of logic in entering these criteria as you did in Step B (for posting requests). The Job Time concerns are a little different. In this case, the default value of 10 seconds would be sufficient to process about 750 requests. You would not need to adjust this default unless you discovered, by running the Incoming Aging Report (see Section H) or using option M on the main menu screen (M - REVIEW MAILBOX STATUS), that you had a greater number of requests waiting in your mailbox.After pressing return, you will be presented with a screen similar to that shown in Figure V-4. This time you will be editing a file named DSNPRFX.REQUESTS.FROM.SYSJCL,
Florida Automated System for Transferring Educational Records
RECEIVE CURRENT REQUESTS
Enter new parameters to override your LCL defaults:
NWRDC system parameters:
Job Class: X
Job Time (Format = "(min,sec)"): XXXXXXXX(,10)
Name of dataset to be created at NWRDC:
DSN (up to 44 chars.): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
'Edit' to edit generated job stream, 'CAN' to cancel: EDIT
|
where DSNPRFX is your default dataset name prefix. This file will contain a JCL stream similar to that contained on pages 6 and 7 of Appendix L. There are the same five lines that you will edit in the same way as you edited the JCL streams in Sections B and C.
In this JCL stream there is only one dataset whose SPACE allocation might possibly need to be reset. This is the dataset with DD name RQSFILE that appears in the middle of page 7 of Appendix L. Its allocation is set to (TRK,(3,3),RLSE), which is sufficient to hold about 2,100 request records. If you anticipate receiving more than this number of requests, you can add 700 requests additional capacity for each (1,1) that you add to the SPACE allocation. For example, you would leave room for 1,400 additional requests (for a total of 3,500) by setting the allocation to (TRK,(5,5),RLSE).
These statements were generated by the System because "current" requests were selected from Figure V-7, above. Also note in the comments section beginning on page 6 of Appendix L that a sending institution can be specified in columns 27 through 33 of the parameter card. This parameter allows you to select only those records that originated from a specific institution.
You may also wish to modify the parameter input line. In addition to the parameters generated by the initiation process, there is an optional parameter (see Appendix W) that can be used with program SRTS02. This is Sending Institution, a seven digit field for the institution code which allows you to specify the records to be selected by the institution that sent them. See Appendix L, JCL for Extracting Requests, for a byte by byte layout of the parameter fields.
There may or may not be any requests waiting for you in your mailbox, so the file that is created may be empty. You will know whether there were any requests by reading the request summary report (DD name RQSUMRY) which is routed to your remote printer.
Edit this JCL stream in the same way as you edited the JCL streams that will execute programs SRTS01 and SRTS03. Then press PF3 to exit the ISPF editor. You will then be presented with a screen similar to the one shown in Figure V-5. Make your selections on this screen in the same way you did previously, press the return key to execute the functions specified and return to the main menu (unless you opted to return to the editor). When you are presented with the main menu, you will have created the JCL stream necessary to retrieve request records from the System.
E. Customize JCL to Receive ResponsesThis time, select the RECEIVE RESPONSES option by typing a 7 on the main menu's COMMAND line and a g in the Generate/Edit/Submit field, and then pressing the return key. You will be presented with a screen that looks similar to the one shown in Figure V-9. This screen has five parameter fields you can fill in:
As with requests, the Selection Criteria field governs the type of records that are to be retrieved by the JCL stream you are going to create. Normally, you will be retrieving those responses in your mailbox that have not yet been delivered, your "current" responses. Retransmission of response records will be dealt with in Section F, below.
To select your current responses, type current in the Selection Criteria field in the upper right of the screen. The next two fields, Beginning and Ending Date, apply only to record retransmissions, so leave them blank. As with request retrieval, Output Type specifies the form in which you wish to receive the response records: as a File, a Printer report, or Both.
Florida Automated System for Transferring Educational Records
RECEIVE CURRENT RESPONSES
Do you want CURRENT requests or do you need to
RETRANSMIT previously received data: XXXXXXXXXX
For a retransmittal of previously transmitted requests enter dates:
mmddyyyy
BEGINNING DATE: XXXXXXXX
ENDING DATE: XXXXXXXX
To select type of response records to be reported,
enter "INT" for Interdistrict records, or
enter "SEC" for Secondary records, or
enter "PST" for Postsecondary records, or
enter "ALL" for All response records: ALL
To select the type of output
enter "F" for a generated file, or
enter "P" for a printed report,
or
enter "B" for both: X
PF3=Main Menu
|
Response Type indicates, for postsecondary institutions, the type of transcript you wish to receive. Postsecondary institutions are permitted to receive either Secondary Transcripts (by typing sec), or Postsecondary Transcripts (by typing pst), or both (by typing all). Districts can receive all three types of records. Interdistrict Records are specified by typing int, Secondaries by typing sec and Postsecondaries by typing pst. Typing all, of course, results in the selection of all types of records available. Any institution can send any type of record to itself, which it may wish to do when it is in the status of Local Testing (see section K of this chapter). When an institution types all, the JCL that is generated includes both print programs (SRTS12IS and SRTS12P) in the event that more than one type of record is available. See Appendix L, JCL to Extract Responses, for an example.
For purposes of this discussion, both a machine-readable file and a printer report will be selected. Having typed the letter b on the next to the last printed line shown in Figure V-9, you will then press the return key. Note that if you wish to cancel the entire operation and return to the main menu you may press the PF3 key.
Florida Automated System for Transferring Educational Records
RECEIVE CURRENT RESPONSES
Enter new parameters to override your LCL defaults:
NWRDC system parameters:
Job Class: X
Job Time (Format = "(min,sec)"): XXXXXXXX(,10)
Name of dataset to be created at NWRDC:
DSN (up to 44 chars.): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
'Edit' to edit generated job stream, 'CAN' to cancel: EDIT
|
You will now be presented with a screen similar to the one shown in Figure V-10. The usual parameters may be entered: Job Class, Job Time, and Output Dataset Name. You followthe same kind of logic in entering these criteria as you did in Section C (for posting responses). The Job Time concerns are roughly the same. In this case, the default value of 10 seconds would be sufficient to process about 50 sets of Interdistrict Records or transcripts. You would not need to adjust this default unless you, for some reason, needed to process a greater volume of responses in a single execution of program SRTS04.
After pressing return, you will be presented with a screen similar to that shown in Figure V-4. This time you will be editing a file named DSNPRFX.RESPONSE.FROM.SYSJCL, where DSNPRFX is your default dataset name prefix. This file will contain a JCL stream similar to that shown on pages 8 through 12 of Appendix L. There are the same five lines that you will edit in the same way as you edited the JCL streams in the sections above.
This JCL stream contains five job steps. The first deletes any file with the same name as the Output Dataset Name specified on the previous screen (just in case an old copy of this file still exists). The second step is the execution of program SRTS04 to retrieve any responses (note the PARAM dataset near the top of page L-9) found in the mailbox. Also note in the comments section starting on page 8 of Appendix L that a sending institution can be specified in columns 30 through 36 of the parameter card. This parameter allows you to select only those records that originated from a specific institution. Step three is the execution of program SRTS03A to produce an edit report of any errors remaining in the response records retrieved in the previous job step. Steps four and five are executions of programs SRTS12IS and SRTS12P. These programs produce the printer reports of Secondary Transcripts and Postsecondary Transcripts, respectively. Had only one type of transcript been requested, only one of these job steps would have been necessary.
Some attention should be paid to the setting of the SPACE allocation for the dataset with DD name RSPFILE (the dataset to which the retrieved responses will be written). Its allocation of (CYL,(1,1),RLSE) is sufficient to hold about 10,000 response records (or about 200 fifty-record transcripts. An additional 10,000 records of space can be added for each (1,1) added to the specification. For example, a setting of (CYL,(3,3),RLSE) would leave room for a total of 30,000 response records (say, 600 transcripts of 50 records each).
You may also wish to modify the parameter input lines. In addition to the parameters generated by the initiation process, there are four optional parameters. With program SRTS04, a seven digit Sending Institution parameter allows you to select records based on the sending institution. For program SRTS12IS, the Output Type parameter allows you to control what data is printed. A value of "P" prints the permanent record/transcript, whereas defaulting to a blank will cause both the permanent record/transcript plus Category B data to be printed. Another parameter allows you to suppress the printing of state grading scale and course flag comment for students below grade nine; a value of >S= suppresses the data, leaving the parameter blank allows the information to be printed. For both programs SRTS12IS and SRTS12P, the Printed Lines per Page parameter, which is a three digit number, allows you to specify how many lines are printed on each page (see Appendix W for a full discussion of this parameter). Both programs also have a parameter that directs the programs to print banner pages when Addressed Institution changes (to facilitate report bursting). See Appendix L (JCL for Extracting Responses Section) or Appendix W for a byte by byte layout of these parameter fields. Program SRTS12P has two more parameters; one that suppresses grade qualifier information; a value of >X= excludes the data, a value of blank allows the data to be printed, and one that suppresses SPEEDE/ExPRESS curriculum code qualifier information; a value of >X= excludes the data, a value of blank allows the data to be printed.
There may or may not be any responses waiting for you in your mailbox, so the file that is created may be empty. You will know whether there were any responses by reading the response summary report (DD name RSSUMRY) which is routed to your remote printer.
Edit this JCL stream in the same way as you edited the JCL streams in the last three sections. Then press PF3 to exit the ISPF editor. You will then be presented with a screen similar to the example shown in Figure V-5. Make your selections on this screen as before and press the return key to execute the functions specified and return to the main menu (unless you opted to return to the editor). When you are presented with the main menu, you will have created the JCL stream necessary to retrieve response records from the System.
F. Record RetransmissionSituations may arise in which you will find it useful to have certain records retransmitted (say, the originally retrieved records were lost or damaged). You can request the generation of a retransmission JCL stream by giving different answers to the questions posed by the screens represented in Figures 8 and 10 (for requests and responses, respectively). Instead of typing the word current in the first field, type the word retransmit. Then fill in the range of access dates for which you wish to retrieve records for retransmission, using the Beginning Date and Ending Date fields. After this screen, everything else is the same as in the case where current (undelivered) records are requested. Note that only delivered records are retrieved when retransmission is selected.
Thus, you can use the screens shown in Figures 8 and 10 to generate retransmission job streams. These will, however, overwrite any request/response receive JCL streams you may already have created. As an alternative, you might simply edit your existing request or response JCL streams when a need for retransmission arises. The statements following the PARAM DD statements in the SRTS02 and SRTS04 job steps (shown on pages L-7 and L-9, respectively) will need to be changed:
| for SRTS02 on page L-7 | for SRTS04 on page L-9 | |
| change | ||
| CURRENT | ALLCURRENT | |
| to | ||
| RETRANSMITmmddyyyymmddyyyy | ALLRETRANSMITmmddyyyymmddyyyy |
where mmddyyyymmddyyyy are the beginning and ending access dates of the date range you wanted to select (for example, 0701198907031989 to retrieve all delivered records accessed between July 1st and 3rd, 1989). You would do this by typing the letter e in the main menu's Generate/Edit field and selecting either option 7 or 8, depending on the JCL stream you wanted to edit. Then, after submitting the retransmission job, you would return to edit mode (again through the main menu) and return the JCL stream to its original state, this time instructing the System to save but not execute the JCL stream.
You will be able to decide which procedure works best for your institution. You may wish to save separate copies of the JCL streams that request current or previously delivered (retransmit) records. You would do this by saving the copies to different datasets. Note that the System can only be used to submit JCL streams stored on datasets DSNPRFX.REQUESTS.FROM.SYSJCL or DXNPRFX.RESPONSE.FROM.SYSJCL, for requests and responses, respectively (where DSNPRFX is your default dataset name prefix). To submit a JCL stream stored on a different dataset, you will need to exit the System and submit the JCL directly from ISPF (a simple procedure, but those not conversant in TSO/ISPF may need to speak with FIRN personnel for instructions as to how this could be done).
Note that retransmission will be necessary if a retrieval job (either requests or responses) terminates due to insufficient time or space allocation. Such a situation might occur if an unexpectedly large number of requests or responses were waiting for you in your mailbox. Say that room had been provided for 200 transcripts, but 500 were in your mailbox. The job would terminate during the 201st response, and 200 of the responses would be marked delivered on the data base. The output file of transcripts would be incomplete, with a partial transcript, possibly, at the end. To recover from this situation, you would do the following:
| - | edit your JCL stream to increase the SPACE allocated to the dataset that receives the records, and to request a retransmission of all records delivered beginning with the last date you executed this JCL stream; |
| - | submit the JCL stream for execution; |
| - | after this execution is complete, re-edit the JCL stream to retrieve current, being sure to change the name of the dataset to which the records are to be written (you don't want to overwrite the dataset with the retransmitted records); |
| - | |
| - | merge the datasets produced by the first and second executions. |
The resulting dataset might contain additional records that you had already received, but no information would be lost.
G. Outgoing Aging ReportIn this section you will create the JCL stream used to execute program SRTS21, the Outgoing Aging Report generator. With this program, you will be able to track the request and response records sent out from your local system as they are posted to your addressees' mailboxes and, ultimately, received by your addressees. Records you send will only remain in the post office data base for a predetermined length of time as stated in section E of Chapter III. Therefore, it is imperative that this program be executed on a regular basis if you wish to have an accurate audit trail for all your outgoing requests and responses.
From the System's main menu, type an 8 on the COMMAND line, a g on the line in the lower right-hand corner labeled Job Stream (G, E, or S) ==>, and press the return key. You will be presented with a screen similar to the one shown in Figure V-11. There are two parameters to be filled in: Output Type (with the standard File, Printer report, or Both options) and Record Status Restriction.
Record Status Restriction is the parameter used to keep redundant information from appearing on the report. Typing a y in this field directs program SRTS21 to ignore those records that had achieved "delivered" status prior to the last time this program was executed with a value of "Y" in the parameter. Typing the letter n, on the other hand, directs the program to report the status of every request and response that you sent out that still remains in the post office data base.
|
Fill in the two parameters and press the return key. You will now be presented with a screen similar to the one shown in Figure V-12. The usual parameters may be entered: Job Class, Job Time, and Output Dataset Name. In this case, the default value of 10 seconds would be sufficient to process about 750 requests and/or response Header Records. Adjust this parameter if you have sent out more messages than that and press the return key.
You will be presented with a screen similar to the one shown in Figure V-4. This time you will be editing a file named DSNPRFX.OUTGOING.FROM.SYSJCL, where DSNPRFX is your default dataset name prefix. This file will contain a JCL stream similar to that shown on pages 13 and 14 of Appendix L. There are the same five lines that you will edit in the same way as you edited the JCL streams in the sections above.
|
In this JCL stream there is only one dataset whose SPACE allocation might possibly need to be reset. This is the dataset with DD name AGEFILE that appears at the end of the stream on page 14 of Appendix L. Its allocation is set to (TRK,(3,3),RLSE), which is sufficient to hold about 2,100 Header Records. If you anticipate receiving more than this number of records, you can add 700 requests additional capacity for each (1,1) that you add to the SPACE allocation. For example, you would leave room for 1,400 additional requests (for a total of 3,500) by setting the allocation to (TRK,(5,5),RLSE).
Edit this JCL stream in the same way as you edited the System's other JCL streams. Then press PF3 to exit the ISPF editor. You will then be presented with a screen similar to the one shown in Figure V-5. Make your selections on this screen and press the return key to execute the functions specified and return to the main menu.
H. Incoming Aging ReportIn this section you will create the JCL stream used to execute program SRTS22, the Incoming Aging Report generator. With this program, you will be able to check the access dates and status of the request and response records that have come into your mailbox. Use this report to assist in the identification of records for retransmission purposes.
From the System's main menu, type a 9 on the COMMAND line, a g on the line in the lower right-hand corner labeled Job Stream (G, E, or S) ==>, and press the return key. You will be presented with a screen similar to the one shown in Figure V-13. There are two parameters to be filled in: Output Type (with the standard file, printer report, or both options) and Access DateRange. Access Date Range must be filled in. There is a field for Beginning Access Date and a field for Ending Access Date, both formatted mmddyyyy.
Florida Automated System for Transferring Educational Records
INCOMING AGING REPORT
Limit the report to a specific range of posting dates:
mmddyyyy
BEGINNING DATE: XXXXXXXX
ENDING DATE: XXXXXXXX
Type of output(s) to be created:
enter "F" for a file of header records only, or
enter "P" for a print report
only, or
enter "B" for both a print report and file of header of records: X
PF3=Main Menu
|
Fill in these parameters and press the return key. You will now be presented with a screen similar to the one shown in Figure V-14. The usual parameters may be entered: Job Class, Job Time, and Output Dataset Name. As with the Outgoing Aging Report generator, the default value of 10 seconds would be sufficient to process about 750 requests and/or response Header Records. Adjust this parameter if there are more messages than that in your mailbox and press the return key.
Florida Automated System for Transferring Educational Records
INCOMING AGING REPORT
Enter new parameters to override your LCL defaults:
NWRDC system parameters:
Job Class: X
Job Time (Format = "(min,sec)"): XXXXXXXX(,10)
Name of dataset to be created at NWRDC:
DSN (up to 44 chars.): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
'Edit' to edit generated job stream, 'CAN' to cancel: EDIT
|
You will be presented with a screen similar to the one shown in Figure V-4. This time you will be editing a file named DSNPRFX.INCOMING.FROM.SYSJCL, where DSNPRFX is your default dataset name prefix. This file will contain a JCL stream similar to that shown on pages 15 and 16 of Appendix L. There are the same five lines that you will edit in the same way as you edited the JCL streams in the sections above.
In this JCL stream there is only one dataset whose SPACE allocation might possibly need to be reset. This is the dataset with DD name AGEFILE that appears at the end of the stream on page 16 of Appendix L. Its allocation is set to (TRK,(3,3),RLSE), which is sufficient to hold about 2,100 Header Records. If you anticipate receiving more than this number of records, you can add 700 requests additional capacity for each (1,1) that you add to the SPACE allocation. For example, you would leave room for 1,400 additional requests (for a total of 3,500) by setting the allocation to (TRK,(5,5),RLSE).
Edit this JCL stream in the same way as you edited the System's other JCL streams. Then press PF3 to exit the ISPF editor. You will then be presented with a screen similar to the one shown in Figure V-5. Make your selections on this screen and press the return key to execute the functions specified and return to the main menu.
I. Participant Status ReportIn this section you will create the JCL stream used to execute program SRTS31, the Participant Status Report generator. With this program, you will be able to get a report and/or file detailing the current level of participation for each institution. Since the System will reject records which are addressed to an institution that cannot electronically accept the data, you can use the output from this program to limit transmission of response records to only those institutions that are in full production mode.
Florida Automated System for Transferring Educational Records
PARTICIPANT STATUS REPORT
Type of output(s) to be created:
enter "F" for a file of participant status records only, or
enter "P" for a print report
only, or
enter "B" for both a print report and file of
participant status records: X
Type of participants to be included in the output(s):
enter "F" for FASTER participants, or
enter "N" for non-FASTER (SPEEDE/ExPRESS) participants, or
enter "B" for both FASTER and non-FASTER institutions: X
PF3=Main Menu
|
From the System's main menu, type a 10 on the COMMAND line, a g on the line in the lower right-hand corner labeled Job Stream (G, E, or S) ==>, and press the return key. You will be presented with a screen similar to the one shown in Figure V-15. Fill in Output Type with the standard File, Printer report, or Both options. Then fill in Participant Type with F (FASTER participants; i.e., Florida public school districts, community colleges, and universities), N (non-FASTER institutions; i.e., non-FASTER participants in the SPEEDE/ExPRESS national electronic transcript system), or B (for both), and press the return key. You will now be presented with a screen similar to the one shown in Figure V-14. The usual parameters may be entered: Job Class, Job Time, and Output Dataset Name. The default value of 10 seconds should be sufficient to process all participants.
You will be presented with a screen similar to the one shown in Figure V-4. This time you will be editing a file named DSNPRFX.PARTSTAT.FROM.SYSJCL, where DSNPRFX is your default dataset name prefix. This file will contain a JCL stream similar to that shown on pages 17 and 18 of Appendix L. There are the same five lines that you will edit in the same way as you edited the JCL streams in the sections above.
Edit this JCL stream in the same way as you edited the System's other JCL streams. Then press PF3 to exit the ISPF editor. You will then be presented with a screen similar to the one shown in Figure V-5. Make your selections on this screen and press the return key to execute the functions specified and return to the main menu.
J. Contacts List ReportIn this section you will create the JCL stream used to execute program SRTS42, the Contacts List Report generator. This program creates a report and/or file containing names, addresses, and phone numbers of key FASTER personnel at each institution. This data is maintained by individuals at each institution using the on-line screens provided for that purpose (see Chapter XI Section E).
From the System's main menu, type an 11 on the COMMAND line, a g on the line in the lower right-hand corner labeled Job Stream (G, E, or S) ==>, and press the return key. You will be presented with a screen similar to the one shown in Figure V-15. Fill in Output Type with the standard File, Printer report, or Both options, and Participant Type with FASTER, Non-FASTER, or Both options, and press the return key. You will now be presented with a screen similar to the one shown in Figure V-14. The usual parameters may be entered: Job Class, Job Time, and Output Dataset Name. The default value of 10 seconds should be sufficient to process all contacts.
You will be presented with a screen similar to the one shown in Figure V-4. This time you will be editing a file named DSNPRFX.CNTCLIST.FROM.SYSJCL, where DSNPRFX is your default dataset name prefix. This file will contain a JCL stream similar to that shown on pages 19 and 20 of Appendix L. There are the same five lines that you will edit in the same way as you edited the JCL streams in the sections above.
Edit this JCL stream in the same way as you edited the System's other JCL streams. Then press PF3 to exit the ISPF editor. You will then be presented with a screen similar to the one shown in Figure V-5. Make your selections on this screen and press the return key to execute the functions specified and return to the main menu.
Once you have completed this section you will have assembled the complete set of JCL streams necessary to execute the System's programs. You will then be ready to proceed with local testing, the next phase of the user initiation procedure.
K. Local Testing ModeWhen you receive your logon ID, FIRN staff will identify your institution to the System as a participant and set your initial participation status to "Local Testing." This permits you to begin working with the System, but informs other users (through the Participant Status Display, described in Chapter XI Section C) that you are not yet ready to exchange records. There are a number of tasks you will need to complete before you can enter the parallel testing phase.
Once you have created and/or downloaded the JCL streams used to execute the programs of the System, your next step should be to download some of the programs themselves (Chapter XII details this process). RJE institutions will need to download programs SRTS05 and SRTS06, to preprocess and postprocess their records. Many institutions will want to download the four report writing programs:
| SRTS11 - | produce the Requests Report from a file of request records (see Appendix T); |
| SRTS12IS - | produce the Secondary to Postsecondary Transcript (in permanent record card format, see Appendix U) from response records; and |
| SRTS12P - | produce the Postsecondary Transcript (see Appendix V). |
| SRTS12CC - | produce the one-page High School or Graduation Summary Transcript (see Appendix U). |
Every institution should download copies of programs SRTS01 and SRTS03. These are the programs that edit your requests and responses, respectively, before posting them in your addressees' mailboxes. The database access portions of the programs have been removed, so you can use them locally as edit programs.
Local Testing begins with the local development of the programs and procedures necessary to permit an institution to take student records and transcripts from its local files and rewrite them according to the System's formats. Until you have accomplished this task, the bulk of your work still lies ahead. You will still be able to use the interactive features of the System described in Chapter XI to make basic contact with other institutions, but this really isn't a truly electronic exchange of student records. An electronic transcript is one that is taken directly from the automated records of one institution and passed through the System to another institution, where automated procedures use the electronic transcript to update the second institution's files. To produce an electronic transcript, you must be able to generate student records in the System's formats from your local data files.
When you have developed the necessary software you should then use it to create a set of test requests and responses. These should list your institution as both sender and addressee. This way, you will be able to put requests in your own mailbox and pick them up. Then you can send the responses and pick those up, too. You will also be able to use the Aging Reports to track the entire process.
Before actually sending out any requests, however, you should first run your test records through your copies of the System's edit programs. This will permit you to gauge the validity of your test records within the friendly confines of your own data center. This way, misunderstandings concerning the formats and their edits can be cleared up before you begin experimenting with the data communications' elements of the System.
At this or any other point in working with the System, if you have any questions, please feel free to contact FIRN. The FIRNMAIL user-ids are designed to facilitate this process, so use them as much as you can.
Once you're confident your test records can pass the System's edits, you will be ready to test the JCL streams you created during User Initiation. Send and pick up your requests and responses. Familiarize yourself with the System's reports and other output. Be especially sure to use the Outgoing Aging Report!
When you have successfully sent and received student records using the System, you will be ready to take the next step. Use the Participant Status Display (as described in the Chapter XI Section C) to change your status to "Parallel Testing." Then use this same facility to determine which of the institutions with whom you normally exchange records is farthest along in the record transfer process. Contact that institution using FIRNMAIL and arrange a test transmission. Then begin to incorporate the use of the System with your normal record processing procedures.