ÿþ<html> <head> </head> <body> <font face="verdana, helvetica, sans-serif" color="#000000" size="2"> <table width="800"> <tr> <td> <font size="2"> <p> <font size="3"><b>Fixing Incorrect Dates and Times Stored by JobRescue and ElectroPage</b></font> <hr /> </p> <p> JobRescue and ElectroPage save four time data values for every $STDLIST and report that is saved. This date and time data is used for <ul> <li>STATUS program display purposes</li> <li>Determining LOG beginning and end times</li> <li>Determining when a saved spoolfile should be deleted</li></ul> </p> <p> All files stored by JobRescue and ElectroPage are uniquely named, and stored in the POSIX file system, under the NSD account. </p> <hr /> <p> <b>Requirements</b></p> <p> <b>This procedure assumes that you are somewhat familiar with JobRescue/ElectroPage, using the STATUS program, and have at least a peripheral knowledge of where JobResuce/ElectroPage store the saved spoolfiles.</b> <ul> <li>You must be signed on as MGR.NSD for this procedure. </li> <li>You must use the Reflection terminal emulator on your PC in order to upload the latest program to your HP3000</li> <li>This procedure works with all JobPak 6.1 versions, A through F.</li> <li>You may leave JobPak running during this procedure. It does not affect the background job or any users using the STATUS program.</li> </ul> </p> <hr /> <p> <b>Download the Correct DATEFIX Program</b></p> <p> On some JobPak distributions a program named <b>DATEFIX.JPAK.NSD</b> may be found. Not everyone has this program. <b>If you do have this program on your system, PURGE IT NOW</b>. You must download the new DATEFIX program and verify its version before you may use it. </p> <p> Download the latest DATEFIX program to your PC at the link <a href="/download/JobPak/DateFix_Jpak_20110728_Labels_Format"> DateFix_Jpak_20110728_Labels_Format</a>.</p> <p> <br> These instructions explain how upload it to your HP3000 using Reflection for Windows. <ol style="line-height: 20pt"> <li>Download the DATEFIX program from the link above.</li> <li>Save the download to a easy to find location on your PC. It is named DateFix_Jpak_20110728_Labels_Format.</li> <li>Log on to your HP3000 using Reflection as MGR.NSD. </li> <li>Select FILE from the menu bar and select TRANSFER from the drop down list. The File Transfer dialog box will be displayed. </li> <li>In the File Transfer dialog box, change the Transfer Type to <b>LABELS</b>. Make sure the Protocol is set to WRQ/Reflection. </li> <li>Locate the DATEFIX download file on the Local side and highlight it.</li> <li>Set the host filename value to <b>DATEFIX.PUB.NSD</b></li> <li>Click on the Transfer button to upload the file to the HP3000.<br> </li> </ol> You should now have the proper DATEFIX.JPAK.NSD program.</p> <p> To verify the version of DATEFIX, enter the command: <ul> <b>WHAT.PUB.NSD DATEFIX.JPAK.NSD</b></ul> </p> <p> The correct version should have a date equal to or later than: <ul> <b>datefix.jpak:<br /> DATEFIX 6.1F(2011/07/28) (C) 2005-2009 Nobix, Inc.</b> </ul> <b>DO NOT CONTINUE IF THE DATE DISPLAYED IS EARLIER THAN 2011/07/28. Although running the wrong version of this program can be fixed, it is a much more time consuming process.</b> </p> <hr /> <p> <b>Make a List</b></p> <p> You must now determine which saved spoolfiles need time correction. For the remainder of this procedure, <b>time correction is always specified in a positive or negative number of seconds.</b> </p> <p> Use the STATUS program to determine which spoolfiles require time correction. You may need to open each suspect spoolfile in STATUS and examine the logon and logoff date/time in order to determine if it should be corrected. Logon time is not as critical as logoff and save time, as logoff and save time are used to determine the spoolfiles age for deletion purposes. <b>Make a list of the file numbers, shown on the left of the SHOW command's display, of those files that need correction.</b> </p> <p> For reports saved in ElectroPage, use STATUS in command line mode and add the ";REPORT" argument to the end of the show command for each LOG. As in: <ul> <b>SHOW @;REPORT</b></ul> Do this for each LOG, or use the SHOWALL command. For reports, the logon time is irrelevant, however the logoff (when the file was closed) and save times should be adjusted. </p> <p> Things to take into consideration: <ul style="line-height: 20pt"> <li>When the time was set incorrectly on the system, what was the date and time supposed to be?</li> <li>When the time was changed on the system, what date and time was actually entered?</li> <li>Did this happen at a reboot or after the system was up and running?</li> <li>Were any jobs running at the moment the date/time was changed?</li> <li>Did any jobs logon when the date/time was set incorrectly?</li> <li>Did any jobs logoff when the date/time was set incorrectly?</li> <li>When the date/time was corrected, were multiple attempts made to correct the date/time or just one SETCLOCK command?</li> </ul> </p> <p> Once you have your list you must now turn that list into the POSIX filenames corresponding to each filenumber shown in STATUS. Your list should be seperated by which files need logon correction, and which need logoff &amp; save time correction. For example, if some jobs were running when the time was set correctly, their logoff/save time will be correct but their logon time might not be. </p> <p> If you are going to have a large set of files that need correction, like you ran this way for a whole day before someone noticed the problem, go into the specifc LOG in the STATUS program and execute the command: <ul> <b>SHOW @;FINFO</b></ul> And for reports it would be <ul> <b>SHOW @;FINFO;REPORT</b></ul> These commands display the POSIX pathname of the files without having to do them on-by-one.</p> <p> Now determine the time correction needed. Time correction is in seconds. The time correction value you specify is going to be added to the time already recorded by JobPak. Adding a negative number adjusts the time backwards. Note that there are 3600 seconds in an hour, and 86400 seconds in a day. </p> <p> If the time was set incorrectly say a year in advance, but the month,day,hour and minute are correct, then the time correction is one year's worth of seconds, which is -31536000 seconds. That's a negative correction.</p> <p> If the hour was set one hour back from the actual time, then the time correction would be a positive 3600.</p> <hr /> <p> <b>Running the DATEFIX Program</b> </p> <p> The DATEFIX program allows adjustment of the four time values recorded by JobPak software. Time in JobPak is always recorded as the number of seconds since 00:00 January 1, 1970. To make an adjustment, the DATEFIX program either adds or subtracts to the stored time values. To subtract, you will specify a negative time correction value. You may specify one, two, three or four of the time correction values. <p> You may use a different value for each of the times JobPak has saved. An example would be for a job that logged on when the time was set correctly, but logged off after someone changed the time to an incorrect value.</p> </p> <p> You must be signed on as MGR.NSD to use the program. Arguments inside brackets are optional. The syntax for DATEFIX is (all on one line) <ul> <b>DATEFIX.JPAK "[-logon &lt;tcval&gt;] [-logoff &lt;tcval&gt;] [-ready &lt;tcval&gt;] [-save &lt;tcval&gt;] &lt;pathname&gt"</b> </ul> Where -logon, -logoff, -ready, and -save each indicate the time correction value to be changed. &lt;tcval&gt; is the time correction value in seconds, either positive or negative.<br /> <br /> Note the quote marks at then beginning and end of the command line arguments.<br /> <br /> &lt;pathname&gt; is the pathname to the JobPak saved spoolfile, relative to the NSD root directory. For example, <ul> <b>files/A.5.12345.12345678</b></ul> Do not specify the "/NSD/" part at the beginning. The &lt;pathname&gt; argument should always begin with the "files" directory part. If the actual file has a ".cmp" extension on it, do not include the extension. </p> <p> <b>Example</b></p> <p> <ul> SABER[MGR.NSD,PUB] datefix.jpak.t61f "-logon -3600 -logoff -3600 -save -3600 -ready -3600 files53/A.23253.1311872442"<br /> <br /> Actual pathname of file is "/NSD/files53/A.23253.1311872442"<br /> Logon time adjusted -3600 seconds<br /> Logoff time adjusted -3600 seconds<br /> Ready time adjusted -3600 seconds<br /> Save time adjusted -3600 seconds<br /> SABER[MGR.NSD,PUB]<br /> </ul> This example has adjusted all the saved time values to be one hour earlier than the values originally recorded by JobPak. </p> <hr /> <p> <b>Rebuilding STATUS LOG Information</b></p> <p> Rebuilding the LOG display for STATUS takes only a few minutes. You should first determine which JobPak version is installed. You may do this by executing: <ul> <b>PRINT BUILD.JPAK.NSD</b></ul> </p> <p> <b>The MERGEDIT Program</b></p> <p> The MERGEDIT.JPAK program is used to rebuild the log information used by the STATUS program. The syntax of the program is <ul> <b>MERGEDIT.JPAK.NSD  -rebuild 0000 </b> </ul> Note the quote marks at then beginning and end of the command line arguments. </p> <p> You can replace the 0000 with the 24-hour time that your STATUS logs switch over, as in 2030 (for 8:30 pm). You can re-execute the MERGEDIT command as many times as you wish until you get it right. </p> <p> After executing the above syntax with the correct cut-over time, if you are using version 6.1F you must also rebuild the LOGBE information.</p> <p> Perform this next MERGEDIT command only if you are using JobRescue 6.1F: <ul> <b>MERGEDIT.JPAK.NSD -logbe</b></ul> </p> <hr /> <p> <b>Call for Help</b></p> <p> If you have any questions and you are on a current support contract with us, please contact Nobix support at support@nobix.com, or (800) 538-3818, or (925) 659-3500. If you need after hours support, call (925) 659-3500, transfer to extension 160 and leave a detailed message. We will call you right back, unless of course you don t leave your phone number. Yes, we have gotten calls in the middle of the night with detailed messages about very urgent problems, but no name or phone number. </p> </font> </td> </tr> </table> </font> </body> </html>