SAS IT side of things
The serial number process is now supported by the SAS Commerce team (Jason Patti, Byron Keith and Chad Blakenbeker). All requests for IT support can be directed to IT.Online.DigiPlat.AG (at least until the Commerce team gets their own AG). There are two scripts. One to notify JMP Biz Ops when the number of remaining serial numbers falls below a certain threshold (750). And a second script that adds more serial numbers by importing them from a directory. Unique versions of each script are created for each version of JMP.
JMP Biz Ops side of things
For each new version of JMP, a new batch of serial numbers needs to be created. Also, when the number of serial numbers falls below a desired threshold (currently set to 750), a notification is sent to Carol Gretz, Tonya Farrington, and Bob Hickey so that more serial numbers can be added to the database.
The basic process for creating new/more serial numbers:
- Tonya generates a new batch of serial numbers and notifies Paul Nelson when that is complete.
- Paul Nelson then runs a perl script that connects to the database and grabs all new records from the BusinessRules table in the database based on timestamp of the records.
- Paul copies the CSV file generated to a machine where he can e-mail a .zip compressed copy of the file to Tonya.
- Tonya grabs the numbers from Paul and pastes them into a text file using Notepad. She confirms that the file is encoded as UTF-8 and saves the file as "jmpxxsn" (note all lowercase), where "xx" equals the JMP version number (e.g. "15").
- She then posts the file to the directory \\sashq\root\dept\www\jmp\snum\
- Lastly, a script maintained by SAS IT adds the serial numbers to the database by importing them from above directory. There's a cron job that will run at ~10:30 am ET (or thereabouts).
