Banner Student / Release Guide / 7.3.2

Section 4 Problem ResolutionsRecruiting Modulewhen SLRROLL was run in Update Mode, the room was not rolled, and theRestrictions prohibit room assignment error was received.If the Must Match field on SLARDEF was unchecked (set to N) for the effective termof the To Term, the assignment still was not rolled, giving the same error. If theattribute was deleted, the room was still not rolled, again giving the same error. Itappeared that once a restriction override was granted on SLARASG, there was nomethod to have SLRROLL create the new assignment.Impact: When a room exists on SLARDEF for a term in which an attribute exists, andwhen a new room term is created for which the attribute is removed, rooms may notbe assigned correctly on SLARASG and may not be rolled on SLRROLL, if theattribute on the old term is such that it would prevent assignment. The processshould be looking at the room term range for the appropriate attribute record.Resolution: The code that references SLRRDEF has been modified to not performeffective term checking. This ignores the relationship between the room definitionrecord and the room attribute definition record, based on the matching of theterms.Note: This problem resolution is delivered with General 7.4.0.1 as well asStudent 7.3.2.ReportSLRSCHE(#1-Y8NUW)Description: An error occurred when the process was run from job submission.Impact: The process would not run to completion in a windows environment.Resolution: The program failed to find data in GJBPRUN table when running in awindows environment, then looped in the error routine. The compare of thegjbprun_job to the variable object-name has been changed to correct this.Recruiting ModuleDocumentationTape Load(#1-1JBJRF)Description: In the Tape Load and Match Processing procedures, under the“Examples of Matching Algorithm Process and Results” section, the second bullet inExample 2 incorrectly stated that the record would be suspended.Impact: The documentation was confusing.Resolution: The second bullet in Example 2 has been corrected to describe amatched record, not a suspended record. It now reads:Student Release 7.3.2 February 200782 Release Guide Confidential