|
|
 |
Why is my class roster file space disappearing?
Symptoms may include an error message when
an attempt is made to register or modify students, or when students
attempt to sign on for the first time. If you are losing class
roster file space in a course where you have added more space,
then my question for you is do you run the GSPBROS utility? If
your answer is yes, then you may need to specify the "TRUNC=NO"
keyword on your GSPBROS control card request.
If you do not specify the "TRUNC=" keyword
on your GSPBROS control card request, it defaults to "YES". The
result of "TRUNC=YES" is after GSPBROS has rebuilt a roster file,
it truncates it to a size that will accommodate the current size
of the class with little room for expansion. Please observe the
following example:
- A class is setup to accommodate 100 students
- 50 students are registered to the class
- GSPBROS is run against the course without
specifying the "TRUNC=" keyword
- The result is the roster file space for this
class will be reduced to only support 50 students. If "TRUNC=NO"
had been specified when running GSPBROS, then the roster file
space would have remained at its allocated size allowing for
support of 100 students.
Changing your GSPBROS control card request to
specify "TRUNC=NO" now will not undo the previous truncation preformed
by GSPBROS. However, it will permit new class size changes to
be retained going forward. For more details on the use of the
GSPBROS utility, please see the PHOENIX System Utilities Guide.
|
|
|
Order
Your Upgrade Today!