| Release 4.0 | Changed the date format in most JSF panels and batch reports to use Gregorian MM-DD-YY instead of the old Julian YY.DDD. This does not affect the way dates are stored in the JSF files. |
| Improved JSF started task performance significantly when parameter CHKDIRBK = Y is being used. This setting caused an unnecessary amount of I-O to the Job History PDS in past releases. | |
| Eliminated corruption of the Job History PDS directory when a MVS/OS390/zOS system outage occurs. This caused some inaccessible members and lost data in previous releases | |
| Added an optional parameter (CALLESM) that will cause JSF panels to check your External Security Managers JESSPOOL class profiles for the ISPF users authority to access the requested job. | |
| Enhanced support for z/OS, by fixing a problem where jobs that exceeded line length or number-of-lines limits were still archived to JSF. This was possible in z/OS sites where six-digit job numbers can be used. JSF works with z/OS six-digit job numbers, although just the last five digits are shown on JSF panels and reports. | |
| Added the REFRESH command to the Jobname Browse List panel to refresh the list of jobs without leaving it. | |
| Allow a wildcard character (*) in the Jobname field on the Job History Restore panel. This lists ALL restorable jobs for the specified date(s). Past releases required entry of at least the first character of the jobname. | |
| Added FBM support for JSF reprints of jobs using Machine print control characters. | |
| Added parameter LINELSYS, which enables a separate number-of-lines limit for syslogs (LINELSYS) and jobs (LINELMIT). | |
| Added the Job History PDS dataset name to batch reports. Helpful for sites running multiple JSF systems. | |
| Added job JSFDSTOP to stop an active JSF started task. It can be scheduled to run before a scheduled run of either of the purge jobs (JSFDPURG or JSFDPRG2). | |
| Fixed a problem that caused lost jobs when purge job JSFDPRG2 spanned midnight. | |
| Release 3.9 | Added year 2000 compatibility. |
| Corrected JSF 3.8 problem with RESTORE of SYSLOGs. | |
| Corrected JSF 3.8 problem with corruption of SYSIDs on VSAM DELETE file when a SYSLOG is deleted from the ISPF panels. | |
| Corrected JSF 3.8 problem with blank Start date for SYSLOGs on VSAM HISTORY REPORT listing jobs and SYSLOGs than can be restored. | |
| Release 3.8 | Output may now be selected by msgclass or destination. |
| If configured to do so by the administrator, JSF will bypass output that contains more than an administrator-configured number of lines. Bypassed output is routed to a msgclass when output selection is done by class. Bypassed output is routed to another destination when output selection is done by JES destination. | |
| JSF will bypass output which has a logical record length (LRECL) greater than 133, since it cannot properly archive it. Bypassed output is routed to a msgclass when output selection is done by class. Bypassed output is routed to another destination when output selection is done by JES destination. | |
| Options module parameters are displayed in the system log by the JSF started task at startup. | |
| In an attempt to keep JSF up, DYNALLOC failures on PSO (Process Sysout) datasets are now retried once before JSF is brought down. | |
| OS/390 compatibility/workaround changes were made. In an effort to allow JSF to run in sites with 4 digit years PRIOR to the completion of the true year2000-compatible JSF, options were added to configure locations of date fields within the options module (defaulted to pre-JSF 3.8 settings). For the same reasons, JSF now uses the updated version of the TIME macro, which may prohibit JSF from running on releases of MVS prior to 5.x. Since none of these pre-5.x versions will support 4 digit years, this is not seen as much of a hardship. As it is now the 2nd quarter of 1997 and less than 1000 days until it is our opinion that any prudent site is on MVS v5 by now. | |
| The VSAM purge program (JSFB0050) now runs above the line, is Y2K compliant and has a new purge criteria, AGE###. AGE### causes JSFB0050 to purge VSAM records which are older than ### days. Purging using a date parameter in the format YYDDD no longer works, instead YYYYDDD must be specified. | |
| Added ability to suppress the IEBCOPY compress of the JSF PDS during JSF's started task startup processing. | |
| Added ability to name the IEBCOPY program name used to compress the JSF PDS at startup. This was added so that users of products which replace IEBCOPY may still use the original IBM version of IEBCOPY to compress their files. Other IEBCOPY 'clones' don't always work properly. | |
| All screens were changed to mixed case to improved readability, some had minor changes made to improve clarity or functionality. | |
| Some minor maintenance was applied, including changes to JCL in the 2 purge jobs. It is recommended that these jobs are looked at carefully if you keep your existing jobs in production. | |
| An ISPF 4.1-based loadlib for the ISPF interface modules is now provided, as older ISPF 2.x-based modules do not work properly on the more current releases of ISPF. | |
| New code is included in the optional 'Requeue exit' (JSFB0032) that shows you how to issue a console action message when particular conditions are met. | |
| Release 3.7 | This was a maintenance release. |
| Release 3.6 | A new alternative purge process (job JSFDPRG2/pgm JSFB004x) provides quicker purge times, primarily for those sites purging large of members on a regular basis. This purge process also produces smaller archive datasets, since only those members being purged are backed up to JSF's numbers offline archives. You may now choose from purging using JSFDPURG or JSFDPRG2, depending on which runs faster in your site. |
| Performance improvements in JSF were made, such as reducing the amount of I/O done to the WORKFILE DD in the JSF started task. See 'Improving JSF Performance' in this manual for more details. | |
| In prior releases of JSF, the CPU time reported by JSF was TCB time. The SRB time reported by JES on the IEF276 message was not being saved or reported. This release finds the SRB time and adds it to the TCB time. As such, all CPU time figures in JSF displays and reports are a sum of these figures. Note that JSF converts xxxx minutes to HHMMMSS format and also 'throws' away fractions of seconds (as JSF always has). | |
| A new user exit allows you to control the requeue destination for abended print. Normally requeued print is routed to 1 of 8 destinations based on MSGCLASS, but abended print was forced to 1 destination via the options module parameter ABENDEST=xxxxxxxx. This release now provides exit point JSFB0033, which is called by the started task and allows you to specify to which destination abend/JCL error/High condition code/NOTCTLG output should be routed. MSGCLASS may also be changed | |
| PDS I/O error related diagnostic messages in the started task were improved and can now provide insight to problem resolution without a dump in many cases. | |
| Improved machine control character support is provided. Previously, all requeued output was printed as FBA, regardless of content. JSF now scans for machine control characters and requeues FBM output properly. Note that mixed format jobs will remain a problem in this area. Likewise, FBM print support from ISPF is not provided. | |
| Some minor maintenance was applied. | |
| Release number was removed from all panels EXCEPT JSFPINIT. | |
| Debug version of JSFB0000 shipped (JSFB9999). | |
| Release 3.5 | Eliminated requirement to specify location of sort programs. |
| Added requeue control exit to started task (JSFB0000). | |
| Release 3.4 | A new utility was added to allow you to tell JSF what dataset and volume purged output resides on after you have manually merged (or moved) purged output file(s) or utilized a tape stacking package that changed a DSNAME and/or VOLSER or otherwise affected a purge dataset name. See Section 8.3 - Updating the VSAM History File. |
| Restore JCL was moved into a PROC (from program JSFI0315) to facilitate sites with pre-JSF 3.3 purged output that might be restored into the JSF 3.3 (and above) database.3. | |
| An error in the security table macro expansion was corrected. This correction affected only those users who had specified jobnames less than 8 characters in length or userids less than 7 characters in length. | |
| A user exit, JSFB0031, was added to allow more user control over the purge process. See Section 8.1, job JSFDPURG and/or JSFDPRG2. | |
| Release 3.3 | Implemented compression of archived data resulting in an average DASD savings of 40%. |
| Added the ability to shut JSF down immediately, with no loss of data, rather than waiting for an active archival to complete. | |
| Added the ability to specify the JSF 'sleep' interval controlling how often JSF checks the JES queue for output to archive. | |
| Added the ability to specify the number of 'sleep' intervals that must expire before JSF performs queued delete processing. This allows waking JSF up every minute, but having the delete process occur at a different interval resulting in less overhead and VSAM SMF record activity. | |
| Added the ability to turn off JSF queued delete processing. | |
| Removed the restriction requiring JSF be installed in a linklist library | |