Adding Flags: Adding Flags
11/2/2020 Update: Flags are applied to the student record at enrollment.
JOBS:
1. NRJGFLP (NRNWFLP3) Flag Feed: Picks up UGS data and updates our flag DB/inventory and nr-courses (F60). It autosubmits every night after midnight. It takes no inputs. It checks the BEGIN-DATE-3 date on *TXTBLS, NRSCHED table, for the SCHED-level entry. If we're before or equal to that date, it processes the record. If we're after that date, it doesn't process the record.
2. NRJGFLG (NRNWFLG2) Flag Ripple: Ripples attribute flags to same-as classes based upon (F60) course relations. It autosubmits every night after midnight. It takes no inputs. If the date the job is running on is equal to or after BEGIN-DATE-3 for any semester on the NRSCHED table, for the SCHED-level entry, it processes the CCYYS values in the AVAILABLE-CCYYS field on the NRSCHED table. If it is prior to that date, it doesn't process the record.
3. Which job runs at 12am on BEGIN-DATE-3 for a semester? (Noted above, but always a question, so documenting) The only date BOTH jobs run for a CCYYS is BEGIN-DATE-3. However, they are not networked and could execute at overlapping times, so the ripple is not reliable, as the flag feed could still be in progress when the ripple runs. Because of this, the Flag Ripple needs a special, one-time am run the morning of BEGIN-DATE-3 by 8am in order for UGS to begin ID'ing manual flag exceptions.
NOTE – if there is an issue with the flag feed discovered AFTER cutoff but before finalizing uniques, flag feed must be turned on for same date that corrected UGS flag feed is loaded to ftp server. Example, UGS sends corrected feed to ftp server on Friday, Sept 15, flag feed BEGIN-DATE-3 should be Sept 15 so the file will load overnight.
TIMING:
NRJGFLP and NRJGFLG run according to the dates indicated in *TXTBLS, E2, NRSCHED, Class-Manager CCYYSSCHED (screenshot below). This table is updated with the new flag dates at the time we rollover a new semester.
This screenshot shows that for 20149 the flag feed's last run (NRJGFLP) and the flag ripple's first run (NRJGFLG) is after 12am on 03/18/2014 to pick-up the last batch of flag data from UGS for 20149. The same day, we ask IT to run NRJGFLG by 8am so UGS can begin work on ID'ing manual flag exceptions to be made. Since NRJGFLG also runs after midnight, this special morning job ensures that the last batch of flag data we received ripples to cross-listings before UGS begins work on their spreadsheets.
The flag feed cut-off date coincides with the week we begin checking Advance Copy, about two weeks prior to live publication.
...
UGS Manual Flag exception spreadsheets should be received at course.schedule@austin.utexas.edu. The bulk of spreadsheet exceptions should be processed early on, with only a handful of exceptions remaining (if any) by 12:00 pm the day prior to online publication of the Course Schedule.
We will send all CSU requests for flag changes to you as we receive them for written approval. Prior to online publication, we will process CSU flag requests as we receive them, making adjustments per your email responses, if needed. Once the course schedule is published online, flags cannot be changed for an existing section, and schedulers must delete the incorrect section(s) and re-add with corrected flag information via CSU.
Please let me know if you have any questions.