Linking to Detached Statements on login
When logging in to REG, you will see the following system message if Detached Statements are running. Detached processes are started and stopped by Student Billing (SBR).
Welcome to OpenVMS (TM) Alpha Operating System, Version V7.2-1 on node ALPHA
Last interactive login on Friday, 19-JAN-2007 11:10:24.03
Last non-interactive login on Thursday, 18-JAN-2007 23:30:00.08
STATEMENT program number(s) to use for billing (04,01,02,03) ?
You should always respond with the numbers shown, to accept the array of detached processes: In this example, enter: 4,1,2,3. In this way, you link your registration activities to student billing, so that system transactions are performed in both the Registration side and the Billing side every time you enroll, drop or add courses to a student's schedule. In other words, as long as your login is linked to the detached processes, you cause the system to create a billing transaction every time you use the enroll, drop, etc options in Registration. The system keeps track of the timing so that after a certain date (this date is recorded in SBR), no changes are made to the student's account.
What does the “2” indicate in the BILL$RECEIVER logical?
$sho logical *receive*
$ SHO LOG *RECEIVE*
(LNM$PROCESS_TABLE)
"BILL$RECEIVER" = "2,01,02,03,04"
The first digit, or parameter, tells the Registration program to ask the “Generate Student’s Bill” question. The numbers after the “2” identify the detached program the system should communicate with.
If the parameter is 1, the REGISTRATION program prompts the user:
Generate Student’s bill <YES> The prompt occurs after the Schedule OK prompt.The user may press RETURN to generate a bill for the student. You may suppress bill generation by entering NO at the verification prompt. If bill generation is suppressed, no schedule changes are reflected on the student’s billing transactions at this time. The next time SBR produces a bill for the student, the changes are reflected.
If the parameter is 2, a bill is generated automatically after the REGISTRATION “Schedule OK” prompt. SBR users detemine whether a hard-copy statement is produced or whether a system file is created. Either way, the transaction is logged on the system and makes statement processing a bit smoother.
Other notes:
Detached billing is an available method which allows the POISE Registration
System to automatically signal the STATEMENT program when changes occur in
student schedules. This facility also permits qualified Registration System
users to initiate bill generation for students whose schedules change. This
capability is controlled by the billing office, which maintains responsibility
for the program.
$ dir users1:[sbr_*]stat82.log
Directory USERS1:[SBR_FLOY]
STAT82.LOG;6
To STOP a detached process:
Call Billing Office and request a detached statement to be "ended."
Notes:
Special "detach" numbers are required for CampusConnect. Use:
81 for Smr I
82 for Fall
83 for Spring
84 for Smr IIA detached process must be running and be coded in the 81 - 84 range before students can see "Account Balance" on CampusConnect.
When setting up CampusConnect detached statement, never use the "no change" option. If you do, the student can see their statement only if a change has occurred since their last viewing.
CampusConnect always functions in estimated mode. The student always sees estimated charges and credits.
When enrollment is performed online through CampusConnect, statements are not automatically generated. Statements must be generated manually by an SBR user for these students.
Qualified Registration System users will see a prompt
“Which statement?” upon login. The user must enter the appropriate detached
statement number(s) if automatic statements are to be generated. For
example, if detached 1 and 2 are running (for summer and fall terms), their
response might be “1,2." (If an
81-84 number is also running, the REG user can ignore these numbers.)
Therefore, to assist REG users in identifying which number to use,
please use:
1, 11, 21, 31, etc for Smr I terms (2nd character is "1");
2, 12, 22, 32, etc. for Fall terms (2nd character is "2");
3, 13, 23, 33, etc, for Spring terms; and
4, 14, 24, 34, etc, for Smr II terms.
Statements can be written to a text file or to a device.
If written to a text file, you must END the process before you can view or
print actual statements from that file. If written to a device, statements
print immediately
when enrollment is completed by Registrar. To send
statements directly to device, enter colon after device name, e.g., LTA10:
(see above)
Any
statement running for an S term will automatically pick up associated T
courses. This means that a detached statement set up for 032S
will include 4T and 5T terms.
CC$bill_receivers are always “81,82,83,84.” When a REG user logs in, these are displayed in parenthesis along with any other receiver numbers running. Can the system NOT show the cc$bill_receivers, since the REG user does nothing with them anyway? They’re just in the way and cause the REG user to have to visually scan through them to find the actual receiver numbers they need to enter in response.
The file SBRSYS_EXE:[SBR.UTILITY]REG_SBR_LOGICALS.COM, which is executed when registration users log in, has been modified. Registration users will no longer see any detached statements in the "80" series.