{"id":16,"category_id":2,"slug":"jes-report-broker","type":null,"name":"JES Report Broker","code":"JRB","content":"<ul>\r\n <li>Deliver reports using FTP, Email, and the Web<\/li>\r\n <li>Render your z\/OS documents on a secure browser just as they appear if printed.<\/li>\r\n <li>Automatically archive, FTP, or Email your JES documents.<\/li>\r\n <li>Convert to PDF, PCL*, or POSTSCRIPT.*<\/li>\r\n <li>AFP support available*<\/li>\r\n<\/ul>\r\n<p>&nbsp;&nbsp;<\/p>\r\n<p>If you have installed MacKinney Print Transform (MPT), you can render AFP (Advanced Function Printing), for example:<\/p>\r\n<p><img alt=\"JES Report Broker\" class=\"screen-image\" src=\"\/public\/multimedia\/userfiles\/image\/JRB\/jrb_main(1).jpg\" width=\"500\" height=\"444\"><\/p>\r\n<hr>\r\n<p><span style=\"font-size: 10pt; font-family: Arial; color: navy;\">*<\/span>with <span style=\"font-size: 10pt; font-family: Arial; color: navy;\"><a href=\"https:\/\/www.mackinney.com\/products\/mainframe-printing\/mackinney-print-transform.html\">MacKinney Print Transform<\/a><\/span><br><br>\r\n<a href=\"\/accounts\/register.html\"><br>\r\n<\/a><\/p>\r\n<p>&nbsp;<\/p>\r\n<p>&nbsp;<\/p>\r\n<p>&nbsp;<\/p>","summary":null,"featured":1,"status":1,"passwords":1,"extended_info":"0","deleted_at":null,"created_at":"2017-11-14T23:21:25.000000Z","updated_at":"2023-05-11T22:41:40.000000Z","sorted_releases":[{"id":947,"parent_id":null,"product_id":16,"release":"4.1","notes":"<p>Adds s<a href=\"file:\/\/\/K:\/MBC22.docx#_Startup_Commands\">upport for new MacKinney License Keys<\/a><\/p>\r\n<p><a href=\"file:\/\/\/K:\/MBC22.docx#_Startup_Commands\"><br><\/a><\/p>","released_on":"2023-09-05T21:05:21.000000Z","deleted_at":null,"children":[{"id":1037,"parent_id":947,"product_id":16,"release":"4.1.51","notes":"<p>Maintenance release<\/p>","released_on":"2026-01-29T18:08:32.000000Z","deleted_at":null},{"id":1033,"parent_id":947,"product_id":16,"release":"4.1.44","notes":"<p>Maintenance release<\/p>","released_on":"2025-11-13T21:27:34.000000Z","deleted_at":null},{"id":1003,"parent_id":947,"product_id":16,"release":"4.1.34","notes":"<p>Maintenance release<\/p>","released_on":"2025-04-22T19:03:04.000000Z","deleted_at":null},{"id":981,"parent_id":947,"product_id":16,"release":"4.1.023","notes":"<p>Maintenance release<\/p>","released_on":"2024-10-09T21:02:44.000000Z","deleted_at":null},{"id":969,"parent_id":947,"product_id":16,"release":"4.1.019","notes":"<p>Maintenance release<\/p>","released_on":"2024-07-23T16:38:35.000000Z","deleted_at":null},{"id":967,"parent_id":947,"product_id":16,"release":"4.1.015","notes":"<p>Maintenance Release<\/p>","released_on":"2024-04-18T21:38:36.000000Z","deleted_at":null},{"id":958,"parent_id":947,"product_id":16,"release":"4.1.006","notes":"<p>Maintenance release<\/p>","released_on":"2023-12-18T16:59:29.000000Z","deleted_at":null}]},{"id":882,"parent_id":null,"product_id":16,"release":"4.0","notes":"<p>Maintenance release.<\/p>","released_on":"2021-09-02T14:39:58.000000Z","deleted_at":null,"children":[{"id":931,"parent_id":882,"product_id":16,"release":"4.0.064","notes":"<p>Maintenance release<\/p>","released_on":"2023-02-15T17:35:59.000000Z","deleted_at":null},{"id":924,"parent_id":882,"product_id":16,"release":"4.0.062","notes":"<p>Maintenance release<\/p>","released_on":"2023-01-26T17:35:54.000000Z","deleted_at":null},{"id":917,"parent_id":882,"product_id":16,"release":"4.0.053","notes":"<p>Maintenance release<\/p>","released_on":"2022-12-02T17:35:49.000000Z","deleted_at":null},{"id":910,"parent_id":882,"product_id":16,"release":"4.0.051","notes":"<p>Maintenance release<\/p>","released_on":"2022-09-15T16:35:43.000000Z","deleted_at":null},{"id":899,"parent_id":882,"product_id":16,"release":"4.0.034","notes":"<p>Maintenance release<\/p>","released_on":"2022-05-03T16:35:38.000000Z","deleted_at":null},{"id":893,"parent_id":882,"product_id":16,"release":"4.0.031","notes":"<p>Maintenance release.<\/p>","released_on":"2022-03-23T16:35:30.000000Z","deleted_at":null},{"id":887,"parent_id":882,"product_id":16,"release":"4.0.024","notes":"<p>Maintenance release.<\/p>","released_on":"2022-02-08T17:35:24.000000Z","deleted_at":null},{"id":885,"parent_id":882,"product_id":16,"release":"4.0.018","notes":"<p>Maintenance release<\/p>","released_on":"2021-12-06T17:35:15.000000Z","deleted_at":null},{"id":881,"parent_id":882,"product_id":16,"release":"4.0.014","notes":"<ul><li><span style=\"color: rgb(0, 0, 0);\">All maintenance from JRB 3.5<\/span>&nbsp;<strong>&nbsp; <\/strong>\r\n  <\/li><li>Support for ZFS<\/li><li><a href=\"http:\/\/www.mackinney.com\/\"><span style=\"color: rgb(0, 0, 0);\">JRB 4.0 introduces database support via DB2<\/span>\r\n  <\/a><\/li><li><a href=\"http:\/\/www.mackinney.com\/\"><span style=\"color: rgb(0, 0, 0);\">Database support provides a technical basis for future, significant functionality additions<\/span><\/a><\/li><\/ul>\r\n<p><a href=\"http:\/\/www.mackinney.com\/\"><br><\/a><\/p>\r\n<p><\/p>","released_on":"2021-09-02T16:35:07.000000Z","deleted_at":null}]},{"id":735,"parent_id":null,"product_id":16,"release":"3.5","notes":"<ul>\r\n <li>Removed auth code 1 AC(1) from all but the initial JRB load modules.<\/li>\r\n <li>Applied all maintenance from JRB 3.4. &nbsp;&nbsp;<\/li>\r\n <li>When the web server is configured to use SSL (SECURE_WEB_PORT) JRB no longer uses any unsecured port.<\/li>\r\n<\/ul>","released_on":"2017-06-08T14:43:51.000000Z","deleted_at":null,"children":[{"id":879,"parent_id":735,"product_id":16,"release":"3.5.122","notes":"<p>Maintenance Release.<\/p>","released_on":"2021-08-30T16:34:12.000000Z","deleted_at":null},{"id":873,"parent_id":735,"product_id":16,"release":"3.5.109","notes":"<p>Maintenance release.<\/p>","released_on":"2021-03-19T16:33:57.000000Z","deleted_at":null},{"id":861,"parent_id":735,"product_id":16,"release":"3.5.86","notes":"<p>Maintenance Release<\/p>","released_on":"2020-08-24T16:34:04.000000Z","deleted_at":null},{"id":848,"parent_id":735,"product_id":16,"release":"3.5.071","notes":"<p>Maintenance release.<\/p>","released_on":"2020-01-22T17:33:50.000000Z","deleted_at":null},{"id":828,"parent_id":735,"product_id":16,"release":"3.5.051","notes":"<p>Maintenance release.<\/p>","released_on":"2019-05-08T16:33:41.000000Z","deleted_at":null},{"id":827,"parent_id":735,"product_id":16,"release":"3.5.048","notes":"<p>Maintenance release.<\/p>","released_on":"2019-04-11T16:33:16.000000Z","deleted_at":null},{"id":813,"parent_id":735,"product_id":16,"release":"3.5.044","notes":"<p>Maintenance release.<\/p>","released_on":"2019-02-27T17:33:31.000000Z","deleted_at":null},{"id":807,"parent_id":735,"product_id":16,"release":"3.5.040","notes":"<p>Maintenance release.<\/p>","released_on":"2018-12-14T17:32:26.000000Z","deleted_at":null},{"id":789,"parent_id":735,"product_id":16,"release":"3.5.033","notes":"<p>Maintenance release.<\/p>","released_on":"2018-09-24T16:32:18.000000Z","deleted_at":null},{"id":781,"parent_id":735,"product_id":16,"release":"3.5.021","notes":"<p>Maintenance release.<\/p>","released_on":"2018-06-11T16:32:47.000000Z","deleted_at":null},{"id":779,"parent_id":735,"product_id":16,"release":"3.5.020","notes":"<p>Maintenance release.<\/p>","released_on":"2018-05-14T16:31:59.000000Z","deleted_at":null},{"id":778,"parent_id":735,"product_id":16,"release":"3.5.019","notes":"<p>Maintenance release.<\/p>","released_on":"2018-05-10T16:31:44.000000Z","deleted_at":null},{"id":749,"parent_id":735,"product_id":16,"release":"3.5.008","notes":"<p>Maintenance release.<\/p>","released_on":"2017-09-20T23:13:40.000000Z","deleted_at":null},{"id":748,"parent_id":735,"product_id":16,"release":"3.5.005","notes":"<p>Maintenance release.&nbsp;<\/p>","released_on":"2017-07-20T23:14:01.000000Z","deleted_at":null}]},{"id":627,"parent_id":null,"product_id":16,"release":"3.4","notes":"<div>Applied JRB 3.2.01 - JRB 3.2.111 Some of these\nmaintenance items added significant functionality.\u00a0<\/div>\n<ol>\n<li>All maintenance from JRB 3.3<\/li>\n<li>TLS Encryption Security Support Added.\u00a0In addition to SSL, JRB\nnow supports TLS (Transport Layer Security) for both FTP and the JRB\ninternal web server. See section SSL_VERSION<\/li>\n<li>Removed All Virtual Storage Control Keywords.\u00a0All virtual\nstorage control keywords ($INIT) are now obsolete.<br>\nFor example: 2K_BUFFERS<br>\n2K_BUFFERS_EXPANSION_INCREMENT<br>\n2K_BUFFERS_STORAGE_LIMIT_TOTAL<br>\n...<\/li>\n<li>Keyword REPORT_NODE_SCAN is Obsolete.<\/li>\n<li>New Required $INIT Keyword START<br>\nSpecifies the JRB 'startup\nmode': HOT, WARM, COLD.<br>\nSee section START<\/li>\n<li>All Messages Generated by C++ Modules Now Being Sent to JRBLOG<br>\nPreviously these messages would appear on SYSPRINT. This change\nintegrates all pertinent messages into JRBLOG.<\/li>\n<li>Support For the Opera Web Browser Added<\/li>\n<\/ol>\n<p>\u00a0<\/p>\n","released_on":"2015-03-02T23:21:25.000000Z","deleted_at":null,"children":[{"id":724,"parent_id":627,"product_id":16,"release":"3.4.080","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2017-01-17T23:21:25.000000Z","deleted_at":null},{"id":722,"parent_id":627,"product_id":16,"release":"3.4.078","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2017-01-05T23:21:25.000000Z","deleted_at":null},{"id":705,"parent_id":627,"product_id":16,"release":"3.4.067","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-09-01T21:21:25.000000Z","deleted_at":null},{"id":701,"parent_id":627,"product_id":16,"release":"3.4.060","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-08-01T21:21:25.000000Z","deleted_at":null},{"id":695,"parent_id":627,"product_id":16,"release":"3.4.051","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-06-16T21:21:25.000000Z","deleted_at":null},{"id":688,"parent_id":627,"product_id":16,"release":"3.4.047","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-04-18T21:21:25.000000Z","deleted_at":null},{"id":681,"parent_id":627,"product_id":16,"release":"3.4.039","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-03-11T23:21:25.000000Z","deleted_at":null},{"id":675,"parent_id":627,"product_id":16,"release":"3.4.029","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2015-12-17T23:21:25.000000Z","deleted_at":null},{"id":649,"parent_id":627,"product_id":16,"release":"3.4.019","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2015-08-06T21:21:25.000000Z","deleted_at":null},{"id":626,"parent_id":627,"product_id":16,"release":"3.4.011","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2015-04-02T21:21:25.000000Z","deleted_at":null},{"id":625,"parent_id":627,"product_id":16,"release":"3.4.008","notes":"\n<p><strong>1.\u00a0Applied all maintenance from JRB 3.3 \u00a0\u00a0<\/strong><\/p>\n<div>\n <strong>2.\u00a0Added TLS encryption security support\u00a0<\/strong>\n<\/div>\n<div>\n In addition to SSL, JRB now supports TLS (Transport Layer Security) \u00a0for both FTP and the JRB internal web server. \u00a0\n<\/div>\n<div>\n See section SSL_VERSION\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>3.\u00a0Removed all virtual storage control keywords<\/strong>\n<\/div>\n<div>\n All virtual storage control keywords ($INIT) are now obsolete.\n<\/div>\n<div>\n \u00a0 \u00a0 \u00a0For example: \u00a0\n<\/div>\n<div>\n \u00a0 \u00a0 \u00a02K_BUFFERS\n<\/div>\n<div>\n \u00a0 \u00a0 \u00a02K_BUFFERS_EXPANSION_INCREMENT\n<\/div>\n<div>\n \u00a0 \u00a0 \u00a02K_BUFFERS_STORAGE_LIMIT_TOTAL\u00a0\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>4.\u00a0Keyword REPORT_NODE_SCAN is obsolete.<\/strong>\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>5.\u00a0Added required $INIT keyword START<\/strong>\n<\/div>\n<div>\n Specifies the JRB 'startup mode': \u00a0HOT, WARM, COLD.\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>6.\u00a0Sends all messages generated by C++ modules to JRBLOG<\/strong>\n<\/div>\n<div>\n Removes them from SYSPRINT\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>7.\u00a0Added support for the Opera web browser\u00a0<\/strong>\n<\/div>\n","released_on":"2015-03-26T21:21:25.000000Z","deleted_at":null}]},{"id":494,"parent_id":null,"product_id":16,"release":"3.3","notes":"\n<p><strong>1. All maintenance from JRB 3.2.\u00a0\u00a0<\/strong><br \/>\n<strong><br \/>\n2. Restructure Document Archive Access Providing Better Web Performance and Lower Overhead<\/strong><br \/>\nRestructures the code used to search for documents in the archive and history. It adds some overhead to JRB startup in exchange for much less (90% less) overhead during a document search. It does this by avoiding a C++ directory traverse whenever possible. It employs an HFS file to 'save' the results of a directory traverse. The\u00a0 HFS file is rebuilt whenever the following is true:<br \/>\na. JRB startup OR INSTALL$GROUP command is issued on the console.<br \/>\nAND<br \/>\nb. JRB detects the $GROUPS member has been updated since the last rebuild.\u00a0\u00a0\u00a0<br \/>\n<br \/>\n<strong>3. Added a Choice of REPORT_NODE_SCAN Intensity. Provides quicker JRB startup.(Also faster INSTALL$GROUP command execution)<\/strong> REPORT_NODE_SCAN=YES; in $INIT is now a \"QUICK\"scan. It uses the current directory traverse save file mentioned in item 2 above.REPORT_NODE_SCAN=DEEP; in $INIT is a more intense scan. It rebuilds the directory traverse save file. It is more accurate, but at a higher cost of overhead.<br \/>\n\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0<br \/>\n<strong>4. New Batch Utility FUNCTION=FIND_STRANDED_GROUPS_DEEP;<\/strong> FIND_STRANDED_GROUPS is now a \"quick\" scan. The DEEP scan is equal to the DEEP scan introduced in item 3 above.<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n<strong>5. Eliminated JRBSUB.<\/strong> Merged JRBSUB with JRBLOG<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n<strong>6. Enabled New Columns to be Displayable in the History Directory Web Page.<\/strong><br \/>\n<br \/>\nThe following columns were not being previous populated in the History Directory Web Page:<\/p>\n<ul>\n <li>ROOM<\/li>\n <li>PAGES_OR_RECS<\/li>\n <li>MAX_CC<\/li>\n <li>FCB<\/li>\n <li>NUM_RECORDS<\/li>\n <li>OUTPUT_DEPT<\/li>\n <li>OUTPUT_TITLE<\/li>\n <li>OUTPUT_NAME<\/li>\n <li>OUTPUT_ADDRESS<\/li>\n <li>EXECUTION_TIME<\/li>\n<\/ul>\n<p><br \/>\n<strong>7. Added ability to Exclude Selection of JES Output based upon DDNAME<\/strong><br \/>\n<strong><br \/>\n8. Removed carriage control requirement for TXT_CAPTURE_FIELD_TYPE=SEARCH.<\/strong><br \/>\nPreviously TXT_CAPTURE_FEILD_TYPE=SEARCH required that the JES output must have carriage control. Now if TXT_CAPTURE_TEXT_LINE=0;\u00a0 is in use the JES output is NOT required to have carriage control.<br \/>\n<strong><br \/>\n9. Web Page Change. The History Restore Dropdown Can Now Force the User to Specify an Expiration for the Document being Restored.<\/strong><br \/>\n<br \/>\nNew Valid Parameter Value for WEBPAGE_HISTORY_RESTORE_WINDOW. The new parameter \"EXPIREONLY\" causes the \"Keep Restored Document Indefinitely\" radio button to be greyed out and disabled.<br \/>\n<br \/>\n<strong>10. Obsolete keywords<\/strong><br \/>\nDELIVERYTYPE=SEQ; now determines the best LRECL dynamically so the following are obsolete:<br \/>\n<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 OFFLOAD_LRECL<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 OFFLOAD_LRECL_DEFAULT<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SEGMENT_OVERRIDE_OFFLOAD_LRECL<br \/>\n<br \/>\n<br \/>\n<strong>11. Keyword processing changes.<\/strong><br \/>\n<strong>a.\u00a0 Obsolete keywords are now automatically REPLACED\/REMOVED.<\/strong><br \/>\nAt JRB startup, obsolete keywords will automatically be replaced with a current keyword or removed. The JRB administrator will no longer be required to manually removed these keywords.<br \/>\n<br \/>\nExample messages:<\/p>\n<p><br \/>\n\u00a0 JRBE513 ** OBSOLETE KEYWORD, WILL BE DYNAMICALLY COMMETED OUT, SEE LOG\u00a0 **<br \/>\n\u00a0 JRBE059 ** ERROR ON LINE:151\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 MEMBER:$INIT\u00a0\u00a0\u00a0\u00a0\u00a0 **\u00a0<br \/>\n\u00a0 * OBSOLETE, COMMENTED OUT BY JRB: OFFLOAD_LRECL_DEFAULT=200;\u00a0\u00a0\u00a0\u00a0<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n\u00a0JRBE529 ** OBSOLETE KEYWORD, WILL BE DYNAMICALLY REPLACED, SEE LOG **<br \/>\n\u00a0JRBE059 ** ERROR ON LINE:120\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 MEMBER:$INIT\u00a0\u00a0\u00a0\u00a0\u00a0 **\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/p>\n<p><br \/>\n<strong>b. Newly Introduced Required Keywords Are Now Automatically Added for you.<\/strong><br \/>\nWhen a new keyword is introduced it will no longer be required to manually add them.\u00a0 If a default can be determined the keyword will be automatically added at startup.<br \/>\n<br \/>\nExample messages:<br \/>\n\u00a0JRBE381 ** REQUIRED KEYWORD WILL BE DYNAMICALLY ADDED:512BYTE_BUFFERS<br \/>\n\u00a0JRBE530 ** KEYWORD ADDED TO MEMBER:$INIT\u00a0\u00a0\u00a0 RECORD #:175\u00a0\u00a0<br \/>\n* THE FOLLOWING RECORD WAS ADDED DYNAMICALLY BY JRB3.3\u00a0\u00a0 03\/29\/2012\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n<strong><br \/>\nc. UPGRADE_OBSOLETE_KEYWORDS\u00a0 Utility Function is now Obsolete.<\/strong><br \/>\nBecause of the new automatic keyword processing at JRB startup this function has been removed.<br \/>\n<strong><br \/>\n12. Optional SMF Record Written Upon Each Web Access of an Archived Document.<\/strong><br \/>\n<strong><br \/>\n13. Optional SMF Record Written Upon Successful FTP Delivery<\/strong><br \/>\n<strong>New Keyword<\/strong> SMF_FTP_DELIVERY_119<br \/>\nThis can be used for chargeback uses or audit trail.<br \/>\n<strong><br \/>\n14. Only One JRB With the Same Name Can be Running at the Same Time.<\/strong><br \/>\nAn attempt to bring up a 2nd JRB with the same name will result in the following message and JRB will terminate.:<br \/>\n\u00a0\u00a0\u00a0 JRBE507 ** A JRB WITH THIS PROCNAME IS ALREADY RUNNING **\u00a0\u00a0<br \/>\n<br \/>\n<strong>15. JRB Batch Utility Will Terminate With Condition Code 16 if it is Unable to Startup.<\/strong><br \/>\nPreviously if there was an environmental or administrative issue that prevented the utility to fully initialize it would end with a zero condition code which indicated incorrectly that the utility ran successfully.<br \/>\n<br \/>\n<strong>16. New Message JRBE508 Provides the FTP Filename that was Delivered.<\/strong><br \/>\nJRBE508 ** FILENAME:TSTDAT18_JOB18283_STD_gary.txt **<br \/>\n<strong><br \/>\n17. New Keyword to Specify Which TCPIP Region Should be Used: TCPIP_JOBNAME<\/strong><br \/>\nThis keyword supports situations where multiple TCPIP regions are being run in the same Z\/os image.<br \/>\n<br \/>\n<strong>18. Protection Against Intrusion by \"Web Crawlers\" added to the Web Server.<\/strong><br \/>\nThis is primarily in the form of the existence of a 'robots.txt' file.\/<br \/>\n<strong><br \/>\n19. AFP transformation Change using MPT.\u00a0 Now supports Mixture of Formdef\/Pagedef.<\/strong><br \/>\nPreviously it was assumed that ALL the DDnames that make up a JES output group used the same Formdef\/Pagedef.\u00a0 JRB can now accommodate each DDname that may have different Formdef\/Pagedef(s).<br \/>\n<br \/>\n<strong>20. New Keyword DELIVERY_FAILURE_NOTIFY_ID_DEFAULT<\/strong><br \/>\n<br \/>\n<strong>21. New Message Indicating Archive HFS is Full.<\/strong><br \/>\nIf an archive delivery fails due to the HFS being full there is now a delivery return code that specifically describes this:<br \/>\n\u00a0JRBE089 ** DELIVERY FAILED,RC=98 HFS MOUNTPOINT OUT OF SPACE<br \/>\nThis message will be issued to the console highlighted and will not roll off without manual deletion.<br \/>\n\"output descriptor=DESC=(2,7)\"<br \/>\n<br \/>\n<strong>22. JES_REPORT_SELECT_QUEUE_DEFAULT\u00a0 is now a Required Keyword<\/strong><br \/>\nSee section 14.2.286 JES_REPORT_SELECT_QUEUE_DEFAULT<br \/>\n<strong><br \/>\n23. Maximum Length of FTP Paths increased to 256.<\/strong><br \/>\n<br \/>\n<strong>24. Provide Ability to Choose Whether Imbedded Spaces are to be Removed from FTP Pathnames.<\/strong><br \/>\nNew Keywords:<br \/>\nFTP_COMPRESS_DIRECTORY_PATH<br \/>\nFTP_COMPRESS_DIRECTORY_PATH_DEFAULT<br \/>\n<br \/>\nThese new keywords are effective on the FTP pathnames specified in the following keywords:<br \/>\n\u00a0FTP_CREATE_DIRECTORY<br \/>\n\u00a0FTP_CREATE_DIRECTORY_DEFAULT<br \/>\n\u00a0FTP_WORKING_DIRECTORY<br \/>\n\u00a0FTP_WORKING_DIRECTORY_DEFAULT<br \/>\n\u00a0SEGMENT_OVERRIDE_FTP_CREATE_DIRECTORY<br \/>\n\u00a0\u00a0\u00a0<br \/>\n<strong>25. WEBPAGE_SIGNON_POPUP_BG_COLOR\u00a0\u00a0 is now an optional keyword.<\/strong><br \/>\nIt is only required when WEBPAGE_SIGNON_POPUP_MSG is also coded.<br \/>\n<br \/>\n<strong>26. Web \"Restore Document From History\" Change.\u00a0 Can now determine back media information from system catalog instead of JRB.<\/strong><br \/>\nNew keyword: WEBPAGE_HISTORY_RESTORE_CATALOG<br \/>\n\u00a0<\/p>\n","released_on":"2012-05-22T21:21:25.000000Z","deleted_at":null,"children":[{"id":597,"parent_id":494,"product_id":16,"release":"3.3.109","notes":"\n<p>\u00a0Maintenance release.<\/p>\n","released_on":"2014-11-17T23:21:25.000000Z","deleted_at":null},{"id":594,"parent_id":494,"product_id":16,"release":"3.3.107","notes":"\n<p>\u00a0Maintenance release.<\/p>\n","released_on":"2014-11-05T23:21:25.000000Z","deleted_at":null},{"id":573,"parent_id":494,"product_id":16,"release":"3.3.098","notes":"\n<p>\u00a0Maintenance release.<\/p>\n","released_on":"2014-07-15T21:21:25.000000Z","deleted_at":null},{"id":563,"parent_id":494,"product_id":16,"release":"3.3.089","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2014-03-11T21:21:25.000000Z","deleted_at":null},{"id":557,"parent_id":494,"product_id":16,"release":"3.3.083","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2014-02-06T23:21:25.000000Z","deleted_at":null},{"id":554,"parent_id":494,"product_id":16,"release":"3.3.076","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-11-05T23:21:25.000000Z","deleted_at":null},{"id":550,"parent_id":494,"product_id":16,"release":"3.3.074","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-09-10T21:21:25.000000Z","deleted_at":null},{"id":545,"parent_id":494,"product_id":16,"release":"3.3.060","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-06-28T21:21:25.000000Z","deleted_at":null},{"id":538,"parent_id":494,"product_id":16,"release":"3.3.055","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-04-24T21:21:25.000000Z","deleted_at":null},{"id":525,"parent_id":494,"product_id":16,"release":"3.3.043","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-02-19T23:21:25.000000Z","deleted_at":null},{"id":524,"parent_id":494,"product_id":16,"release":"3.3.040","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-01-31T23:21:25.000000Z","deleted_at":null},{"id":523,"parent_id":494,"product_id":16,"release":"3.3.037","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-01-17T23:21:25.000000Z","deleted_at":null},{"id":515,"parent_id":494,"product_id":16,"release":"3.3.023","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-10-29T21:21:25.000000Z","deleted_at":null},{"id":512,"parent_id":494,"product_id":16,"release":"3.3.017","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-09-26T21:21:25.000000Z","deleted_at":null},{"id":503,"parent_id":494,"product_id":16,"release":"3.3.015","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-07-30T21:21:25.000000Z","deleted_at":null},{"id":498,"parent_id":494,"product_id":16,"release":"3.3.007","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-06-05T21:21:25.000000Z","deleted_at":null},{"id":497,"parent_id":494,"product_id":16,"release":"3.3.005","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-06-04T21:21:25.000000Z","deleted_at":null}]},{"id":403,"parent_id":null,"product_id":16,"release":"3.2","notes":"<p><strong>1. Added PAGESORT.<\/strong> Ability to sort document pages\nbased upon sort fields found in the document pages.<br>\nPick any number of \"fields\" within a page to sort on. JRB will sort the\ndocument pages based on the field(s) while performing a document\ndelivery.\u00a0<br>\n<em>Example:<\/em>\u00a0 Sort a document to bring all the pages for a\nparticular customer # together.<br>\n<br>\n<strong>2. Added ability to insert text (plain and AFP) into a document\nas it is being delivered.<\/strong><br>\nCan insert Plain text and AFP text into a document. Provides a range of\npossibilities from adding pages to inserting OMR (Optical Mark\nRecognition).<br>\n<em>Example:<\/em>\u00a0 Insert OMR marks into a document that can be\nread by a postage sorter\/stuffer to minimize postage costs.<br>\n\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0<br>\n<strong>3. Added ability to capture text fields on each\npage.<\/strong>Populate new substitution variable\n&TC(<em>n<\/em>).<br>\n<em>Example:<\/em> Capture a field on a page to be used as the email\naddress to deliver the page. .<br>\n<br>\n<strong>4.<\/strong> <strong>JRB can now Archive the following document\ntypes directly:\u00a0<br><\/strong>\n<strong>\u00a0\u00a0\u00a0\u00a0<\/strong><strong>.CSV<\/strong><br>\n<strong>\u00a0\u00a0\u00a0\u00a0<\/strong><strong>.PS<br><\/strong><strong>\u00a0\u00a0\u00a0\u00a0<\/strong><strong>.PCL<\/strong><br>\n<em>Example:\u00a0<\/em> You have a EXCEL file (comma delimited). You\ncan now archive it directly into JRB for access by your customers via a\nbrowser. Also supports POSTSCRIPT and Printer Control Language\ndocuments.<br>\n<br>\n<strong>5.<\/strong> <strong>Can now control the width and title of\ncolumns on the document directory webpage.<\/strong><br>\nCustomize your JRB web page document directory. You have always been\nable to pick the columns (Jobname, report name, date\/time, formid\u00a0\netc..) and the order in which they appear. Now you can specify the\ntitle of each column so it fits the needs of your user community. You\ncan also set the width (in pels) of each column.<br>\n<strong><br>\n6. On history restore window you can now specify max\/min\/default\ndays-to-retain.<\/strong><br>\nCustomize your JRB ARCHIVE web pages. When a user clicks on a history\ndocument to restore it they have always been presented with a window to\nspecify how many days the document will remain before expiration. Now\nthey are provided with a pulldown list of days.. the JRB administrator\ncan specify the min\/max days to retain that will be presented as well\nas the \"default\"\u00a0 number of days.<br>\n<br>\n<strong>7.<\/strong> <strong>All maintenance from JRB 3.1.\nHighlights:<\/strong><br>\n\u00a0\u00a0\u00a0 <em>a)<\/em> New webpage report directory\ncolumn-\u00a0 \"NUMBER of PAGES\"<br>\n\u00a0\u00a0\u00a0 <em>b)<\/em> Can now select document from JES based\non the \"transaction JOBNAME\"<br>\n\u00a0\u00a0\u00a0 <em>c)<\/em> New substitution variable &JCLTITL.\nFrom TITLE JCL parm.<\/p>\n","released_on":"2010-10-07T21:21:25.000000Z","deleted_at":null,"children":[{"id":456,"parent_id":403,"product_id":16,"release":"3.2.048","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2011-08-10T21:21:25.000000Z","deleted_at":null},{"id":413,"parent_id":403,"product_id":16,"release":"3.2.025","notes":"\n<p>\u00a0Maintenance release.<\/p>\n","released_on":"2011-01-10T23:21:25.000000Z","deleted_at":null},{"id":410,"parent_id":403,"product_id":16,"release":"3.2.023","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2010-12-15T23:21:25.000000Z","deleted_at":null}]},{"id":364,"parent_id":null,"product_id":16,"release":"3.1","notes":"\n<ul>\n <li>JES report selection now includes job return codes.<br \/>\n You can now select JES output based upon the success or failure of the job. This can be useful by segregating job output that 'failed'. You can also use email to notify that a job failed.<br \/>\n New keywords:<br \/>\n 11.2.208 JES_REPORT_SELECT_JOB_CONDITION<br \/>\n 11.2.215 JES_REPORT_SELECT_MAXRC_THRESHOLD<\/li>\n <li>New keywords:<br \/>\n Provides ability to override the number of days history is to be kept for a document segment.<br \/>\n 11.2.421 SEGMENT_OVERRIDE_HISTORY_DAYS_TO_RETAIN<br \/>\n 11.2.422 SEGMENT_OVERRIDE_HISTORY_DISPOSITION<\/li>\n <li>Increased maximum number of route entries to 12,000<\/li>\n <li>All 3.0 maintenance.<br \/>\n JRB 3.0.01 - JRB 3.0.15 have been applied.<\/li>\n<\/ul>\n","released_on":"2009-10-23T21:21:25.000000Z","deleted_at":null,"children":[{"id":386,"parent_id":364,"product_id":16,"release":"3.1.022","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2010-03-25T21:21:25.000000Z","deleted_at":null},{"id":382,"parent_id":364,"product_id":16,"release":"3.1.015","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2010-02-18T23:21:25.000000Z","deleted_at":null}]},{"id":284,"parent_id":null,"product_id":16,"release":"3.0","notes":"\n<p>Added ability to process AFP (Advanced Function Printing) documents using MacKinney Systems Transform (MPT).\u00a0 With MPT, JRB can now transform AFP documents into PDF, PCL or Postscript. The resulting documents will contain all fonts, overlays, graphics and formatting of the original AFP document.\u00a0 When used with archiving, JRB can now render your AFP documents on your browser just as they would look printed.<\/p>\n","released_on":"2009-06-02T21:21:25.000000Z","deleted_at":null,"children":[{"id":328,"parent_id":284,"product_id":16,"release":"3.0.012","notes":"\n<ul>\n <li>Specify a document 'generation' limit for an archive group.<\/li>\n <li>Sets a return code if no documents are selected for backup.<\/li>\n <li>Adds keywords to exclude reports from selection from JES.<\/li>\n <li>Send any raw SITE commands to the FTP server using new keyword: FTP_QUOTE_COMMAND<\/li>\n <li>Specify unlimited number of email addresses (notify also).\u00a0<\/li>\n<\/ul>\n","released_on":"2009-09-04T21:21:25.000000Z","deleted_at":null}]},{"id":283,"parent_id":null,"product_id":16,"release":"2.5","notes":"\n<ol>\n <li>All maintenance available for 2.4 has been applied to 2.5<\/li>\n <li>Required change to $INIT keyword LOCAL_HFS_ROOT<\/li>\n <li>Required change to $INIT keyword CONCURRENT_TCP_CONNECTS_PER_SUBTASK<\/li>\n <li>All C programs have been re-written to XPLINK C++ and the Language Environment has been re-written to use 'PIPI' interfaces.\u00a0 The bottom line is better performance and access to additional functionality.<\/li>\n <li>Archive Compression now available.<\/li>\n <li>New utility function to compress archive documents.<\/li>\n<\/ol>\n","released_on":"2009-05-13T21:21:25.000000Z","deleted_at":null,"children":[]},{"id":170,"parent_id":null,"product_id":16,"release":"2.4","notes":"\n<ol>\n <li>You can now specify the sensitivity level of an EMAIL.<br \/>\n EMAIL_SECURITY_SENSITIVITY_DEFAULT<br \/>\n EMAIL_SECURITY_SENSITIVITY<br \/>\n SEGMENT_OVERRIDE_EMAIL_SECURITY_SENSITIVITY<\/li>\n <li>Ability to control the colors of the hyperlinks to documents on the report directory web page.<br \/>\n A link also now changes color after you have visited that document.<br \/>\n New required keywords:<br \/>\n WEBPAGE_REPORTDIR_UNVISIT_LINK_COLOR<br \/>\n WEBPAGE_REPORTDIR_VISIT_LINK_COLOR<\/li>\n <li>Can now display number of records in a document on the report directory web page.<br \/>\n New valid parameter for keyword WEBPAGE_REPORTDIR_COLUMN_NAME<\/li>\n <li>You can now use any size picture file for the web screen banner, or have no banner at all.<br \/>\n Previously the banner file specified by the keyword WEB_BANNER_FILENAME had to be 450x90<br \/>\n pixels. Now you can specify a picture file of ANY size. If you do not want a banner picture at all you<br \/>\n can now specify 'none'.<br \/>\n WEB_BANNER_FILENAME<\/li>\n <li>You can now control the background color of the web pages.<br \/>\n New required keyword WEBPAGE_BG_COLOR.<\/li>\n <li>Ability to turn off the scrolling effect on the status line of the report directory web page.<br \/>\n New required $WEB keyword WEBPAGE_REPORTDIR_SCROLL_STATUS.<\/li>\n <li>A change to the 'Send report to JES' popup window.<br \/>\n It now displays the 'OK' button first, then the 'Cancel' button to be consistent with other popup windows.<\/li>\n<\/ol>\n","released_on":"2008-01-22T23:21:25.000000Z","deleted_at":null,"children":[]},{"id":182,"parent_id":null,"product_id":16,"release":"2.3","notes":"\n<ol>\n <li>All maintenance available for 2.2 has been applied to 2.3.<br \/>\n JRB 2.2.01 - JRB 2.2.46 have been applied.<br \/>\n \u00a0<\/li>\n <li>You now have control of the number of route entries delivering simultaneously. New keywords for $INIT: \n <ul>\n  <li>DELIVERY_TCLASS_DEFAULT -<br \/>\n  default TCLASS for deliveries.\u00a0 (required keyword)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS1 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS2 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS3 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS4 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS5 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n <\/ul>\n <\/li>\n <li>New keywords for route entries:<br \/>\n DELIVERY_TCLASS - sets TCLASS for a specific route entry.<br \/>\n \u00a0<\/li>\n <li>The above keywords implements a maximum active number of tasks in each of five classes.\u00a0 To implement: \n <ul>\n  <li>Decide how many route entries you want to allow for each TCLASS.<\/li>\n  <li>Specify the TCLASS for each route entry.<br \/>\n  You can use a combination of.<br \/>\n  DELIVERY_TCLASS_DEFAULT<br \/>\n  DELIVERY_TCLASS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n  TCLASS has no effect on priority.... There are other keywords for that.\u00a0 It simply controls the maximum number of concurrently delivering route entries in a given TCLASS.<\/li>\n  <li>Drastic reduction in resource usage.<br \/>\n  <br \/>\n  <span style=\"display: none;\">\u00a0<\/span><\/li>\n <\/ul>\n <\/li>\n <li>Changes have been made to the internal task dispatcher.\u00a0 Previous versions maintained an internal JRB task for each route entry started.\u00a0 This version will require an internal JRB task ONLY when a particular route entry is actually delivering.\u00a0 This will result in a drastic reduction in the numbers of internal tasks, and their buffers, required for a given throughput.\u00a0 The bottom line will be a much leaner JRB.\u00a0 The real storage needed for a given amount of throughput will drop dramatically. This will show up in the following: \n <ul>\n  <li>Smaller real storage demands for JRB<\/li>\n  <li>Smaller value for MAX_NUMBER_INTERNAL_TASKS<\/li>\n  <li>Smaller value for 2K_BUFFERS<\/li>\n  <li>Smaller numbers of transmit buffers allocated.<\/li>\n  <li>Smaller number of JES read buffers<br \/>\n  \u00a0<\/li>\n <\/ul>\n <\/li>\n <li>These changes will show up on your z\/OS monitor (or SDSF) and the values reported by the SHOW command.\u00a0 Also it will show up in the tasks reported by the DISPLAYTASK command (compared to previous versions).<\/li>\n<\/ol>\n<p>\u00a0<\/p>\n<p>The following changes were implemented by maintenance items in JRB 2.3 and carried forward to JRB 2.4<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.26<br \/>\n===========<\/p>\n<ol>\n <li>Provides the ability to specify a codepage to be used when converting a document from EBCDIC to<br \/>\n ASCII.<br \/>\n New (required) keyword:<br \/>\n ASCII_CODEPAGE_DEFAULT<\/li>\n <li>Provides a new, optional, customizable message issued at delivery time.<br \/>\n New keyword:<br \/>\n DELIVERY_MSG_E422_DEFAULT<br \/>\n DELIVERY_MSG_E422<\/li>\n<\/ol>\n<p><br \/>\n===========<br \/>\nMAINT 2.3.26<br \/>\n===========<\/p>\n<p>Provides an extension to the INLINECNTL feature added in maint 2.3.24. You now have control of the processing that occurs if the value of the substitution variable &IC is NOT captured from an INLINECNTL record imbedded in the document to be delivered.<br \/>\n<br \/>\nNew keywords:<br \/>\nINLINECNTL_FIELD_DEFAULT_VALUE<br \/>\nINLINECNTL_FIELD_FAIL<\/p>\n<p>The keyword REPORT_SEPARATOR_USERID can now include any of the supported substitution variables.<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.24<br \/>\n===========<br \/>\nProvides the ability to specify a 'control' record that is imbedded in the report to be delivered. These control<br \/>\nrecords can specify delivery parameters and influence the way the report is delivered and split up.<br \/>\nNew keywords:<br \/>\nINLINECNTL_FIELD_COLUMN<br \/>\nINLINECNTL_FIELD_LENGTH<br \/>\nINLINECNTL_FIELD_TYPE<br \/>\nINLINECNTL_NAME<br \/>\nINLINECNTL_SEARCH_COLUMN<br \/>\nINLINECNTL_TEXT<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.21<br \/>\n===========<br \/>\nAdds a new FUNCTION called FIND_STRANDED_GROUPS to the JRBMUTIL batch utility program.<br \/>\n<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.20<br \/>\n===========<br \/>\nAdded support for mixed-case passwords on the web signon page with a new required keyword,<br \/>\nWEBPAGE_PASSWORD_CASE_SENSITIVE.<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.19<br \/>\n===========<br \/>\nAdded the capability to select reports from the Held queue via the following new keywords:<br \/>\nJES_REPORT_SELECT_QUEUE=HELD;<br \/>\nJES_REPORT_SELECT_QUEUE_DEFAULT=HELD;<br \/>\n<br \/>\nWhen these keyword(s) are not present then reports will be selected from the Output queue, which is the<br \/>\ndefault when neither HELD nor OUTPUT is specified.<br \/>\n===========<br \/>\n<br \/>\nMAINT 2.3.18<br \/>\n===========<br \/>\nAdded a new possible value to following keywords:<br \/>\nARCHIVE_DYNAM_GROUP_DISPLAY=BOTH_NAME_FIRST;<br \/>\n<br \/>\nREPORT_GROUP_TREE_DISPLAY=BOTH_NAME_FIRST;<br \/>\n<br \/>\nREPORT_GROUP_TREE_DISPLAY_DEFAULT=BOTH_NAME_FIRST;<br \/>\n<br \/>\nThis provides the ability to customize the report group tree web page to display the name of the group first, followed<br \/>\nby the description... separated by a dash ('-').<br \/>\n<br \/>\n=========<br \/>\nMAINT 2.3.13<br \/>\n=========<br \/>\nProvides support for new substitution variable &SP. A single space will be substituted in its place. The<br \/>\nsubstitution will take place AFTER the normal blank compression. It can be used to place a space in keywords<br \/>\nwhose values have all spaces normally compressed such as:<br \/>\nFTP_WORKING_DIRECTORY<br \/>\nFTP_CREATE_DIRECTORY<br \/>\n<br \/>\n=========<br \/>\nMAINT 2.3.10<br \/>\n=========<\/p>\n<p>Added support for the ROOM parameter from the OUTPUT JCL statement.<\/p>\n<ol>\n <li>WEBPAGE_REPORTDIR_COLUMN_NAME now accepts the value OUTPUT_ROOM. It adds a column to the report directory web page.<\/li>\n <li>WEBPAGE_REPORTFILT_FILTER_NAME now accepts the value OUTPUT_ROOM. It adds an option to use this value to filter the report directory web page.<\/li>\n <li>Support for the ROOM parameter was extended into the 'Send Report to JES' function from the report directory web page.<\/li>\n <li>New required keyword in the $WEB member. WEBPAGE_REPORTDIR_OUTPUT_ROOM_LEN<\/li>\n<\/ol>\n<p><br \/>\n=========<br \/>\nMAINT 2.3.06<br \/>\n=========<\/p>\n<ol>\n <li>Added ability to specify a variable in these keywords:<br \/>\n EMAIL_FROM<br \/>\n EMAIL_FROM_DEFAULT<\/li>\n <li>Changed message JRBE089. No provides a description of a delivery failure. Provides a short description of the return code in event of a delivery failure. Previously only a return code was provided.<\/li>\n <li>Fixed a problem with EMAIL_TO when a variable was used. The variable was effective to the extent that the email was sent to the correct address however the REPLY address still contained the raw variable (it had not been substituted with the value of the variable).<\/li>\n <li>New message JRBE409 that indicates the completion of a delivery.<\/li>\n<\/ol>\n<p><br \/>\n=========<br \/>\nMAINT 2.3.02<br \/>\n=========<br \/>\nAdded new substitution variable &ACCT(n).<br \/>\nAccounting Information fields from JOB card. n is the relative position of the parameter desired.<br \/>\nFor an example of its use see FTP_FILENAME<\/p>\n","released_on":"2007-02-07T23:21:25.000000Z","deleted_at":null,"children":[]},{"id":183,"parent_id":null,"product_id":16,"release":"2.2","notes":"\n<ol>\n <li>New keyword: SEGMENT_OVERRIDE_JESDELIVERY_COPIES<\/li>\n <li>New keyword: TCPIP_COMPUTER_ASSOCIATES.<br \/>\n Provides compatibility for those customers running CA\/ACCESS.<\/li>\n <li>All of the maintenance applied to JRB 2.1. They are listed below: \n <ol>\n  <li>Provides ability to optionally add a line (maximum 130 characters) to the separator page.<br \/>\n  New keywords:<br \/>\n  REPORT_SEPARATOR_TEXT_DEFAULT<br \/>\n  REPORT_SEPARATOR_TEXT<\/li>\n  <li>Provides ability to specify email addresses via JCL.<br \/>\n  New keywords:<br \/>\n  EMAIL_OBTAIN_ADDRESS_FROM_JCL<br \/>\n  EMAIL_OBTAIN_ADDRESS_FROM_JCL_DEFAULT<\/li>\n  <li>Provides ability to specify what IP address the web server listens to connects on.<br \/>\n  New keyword: WEB_IP@<\/li>\n  <li>Archive Group Dynamic Creation<br \/>\n  Provides ability for JRB to dynamically create new archive groups dynamically without manually defining them in the $GROUPS member.<br \/>\n  New keywords:<br \/>\n  ARCHIVE_DYNAM_GROUP_CAPABLE<br \/>\n  ARCHIVE_DYNAM_GROUP<br \/>\n  ARCHIVE_DYNAM_MOTHER_GROUP<\/li>\n  <li>Ability to split up reports using CONTROLBREAKS<br \/>\n  Define the location within a report that contains a field. Each time that field changes from one page to another a CONTROLBREAK will occur. The previous report segment will end and other will begin. This feature is especially powerful when used with Archive Group<br \/>\n  Dynamic Creation.<br \/>\n  New keywords:<br \/>\n  CONTROLBREAK_NAME<br \/>\n  CONTROLBREAK_BOUNDARY<br \/>\n  CONTROLBREAK_TEXT_COLUMN<br \/>\n  CONTROLBREAK_TEXT_LENGTH<br \/>\n  CONTROLBREAK_TEXT_LINE<\/li>\n  <li>Can use segmentation in conjunction with CONTROLBREAKS<br \/>\n  In order to select the section of a report that is applicable to a CONTROLBREAK, segmentation can be used in conjunction.<\/li>\n  <li>NEW variable &CB(n).<br \/>\n  Will be replaced with the report text value associated with CONTROLBREAK in relative position n within the route entry. It can be used in conjunction with CONTROLBREAKS and Archive Group Dynamic Creation to build the name of the new group being created. Can also be used in REPORT_NAME or any other field that supports variables.<\/li>\n  <li>NEW function for the JRB utility.<br \/>\n  FUNCTION=UPGRADE_OBSOLETE_KEYWORDS<br \/>\n  If JRB detects the use of an obsolete keyword upon startup it will issue the message JRBE381 and terminate. You can use this new function of the JRB utility to automatically upgrade your keywords to the correct format.<\/li>\n  <li>Restructured the manual. Split sections previously in section IV into their own sections.<br \/>\n  New keywords: SSL_FTP_CERTIFICATE_LABEL<br \/>\n  SSL_FTP_CERTIFICATE_LABEL_DEFAULT<\/li>\n  <li>Provides SSL Client authentication for FTP deliveries<br \/>\n  Optionally, FTP servers and require that clients provide a digital certificate.<br \/>\n  This change supports that requirement.<br \/>\n  New keywords: SSL_FTP_CERTIFICATE_LABEL<br \/>\n  SSL_FTP_CERTIFICATE_LABEL_DEFAULT<\/li>\n  <li>Manual sections dealing with SSL support have been re-organized and clarified.<\/li>\n  <li>Re-structured the Archive and History in HFS.<br \/>\n  As a result documents will now be shown on the web pages from newest to oldest.<br \/>\n  = I M P O R T A N T N O T E =<br \/>\n  BEFORE YOU BRING UP JRB you MUST run the batch utility using the new utility keyword FUNCTION=UPGRADE_ARCHIVE; Failure to do so will cause the archive to become unusable until the UPGRADE_ARCHIVE is run.<\/li>\n  <li>Change to ARCHIVE to JES.<br \/>\n  The confirmation pop-up window now provides the ability to specify the following characteristics of the report placed on JES: \n  <ul>\n   <li>OUTPUT CLASS<\/li>\n   <li>FORMID<\/li>\n   <li>DESTINATION<\/li>\n  <\/ul>\n  <\/li>\n  <li>Change to keywords<br \/>\n  JESDELIVERY_FORM<br \/>\n  JESDELIVERY_FORM_DEFAULT<br \/>\n  SEGMENT_OVERRIDE_JESDELIVERY_FORM<\/li>\n  <li>NEW DELIVERYTYPE=REQUE;<br \/>\n  This new deliverytype does not actually deliver a report, is simply changes the<br \/>\n  JES characteristics of a report. It does not create a new JES output like DELIVERTYPE=JES<br \/>\n  does, it just changes the characteristics of the original report.<br \/>\n  New keywords: JES_REPORT_REQUE_NODE_DESTID<br \/>\n  JES_REPORT_REQUE_NODE_DESTID_DEFAULT<\/li>\n  <li>DIRECTORY WEB PAGE FILTER WINDOW CHANGES:<br \/>\n  1. With multiple report directory windows open each one of them may now have a filter window associated with it. Previously only the first directory window could have a filter window.<br \/>\n  2. Removed the alert window that popped up when the 'FILTER OFF\" button was pressed.<br \/>\n  3. The 'FILTER OFF\" button is now 'grayed out' and disabled unless there is actually a filter window open.<br \/>\n  4. All filter fields now translate all input into upper case except for the 'PROGRAMMER NAME' field.<br \/>\n  5. The 'CREATION DATE TO\/FROM' fields initial values have changed: \n  <ul>\n   <li>The 'TO DATE' is now the date obtained from JRB, previously it was the date obtained from the workstation.<\/li>\n   <li>The 'FROM DATE' is now calculated from the 'TO DATE'.<br \/>\n   A number of days are subtracted from the 'TO DATE' to obtain the 'FROM DATE'. The number of days subtracted are obtained from:<br \/>\n   New keyword:<br \/>\n   WEBPAGE_REPORT_FILTER_FROM_DATE_OFFSET<span style=\"display: none;\">\u00a0<\/span><\/li>\n  <\/ul>\n  <\/li>\n  <li>New keywords:<br \/>\n  FTP_TCPIP_READ_TIMEOUT<br \/>\n  FTP_TCPIP_READ_TIMEOUT_DEFAULT<\/li>\n  <li>New option for keyword FTP_MODE and FTP_MODE_DEFAULT.<br \/>\n  You can now specify<br \/>\n  FTP_MODE=PASSIVE_POSTCONNECT<\/li>\n  <li>Changed the FTP protocol associated with FTP_MODE=PASSIVE;<br \/>\n  Some FTP servers were causing deliveries to hang up. Tracing revealed JRB waiting upon a TCP\/READ attempting to receive the response of a 'STOR' FTP command.<\/li>\n <\/ol>\n <\/li>\n<\/ol>\n<ul>\n <li>Previously JRB would: Issue 'PASV', Issue 'STOR', then connects to the server. (PASV,STOR,CONNECT) Now JRB will: Issue 'PASV', connect to the server, then Issue 'STOR'.(PASV,CONNECT,STOR)<\/li>\n <li>In order to preserve previous functionality that might be required from some servers FTP_MODE=PASSIVE_POSTCONNECT now will use the old protocol. (PASV,STOR,CONNECT)<\/li>\n<\/ul>\n","released_on":"2006-06-15T21:21:25.000000Z","deleted_at":null,"children":[]},{"id":184,"parent_id":null,"product_id":16,"release":"2.1","notes":"<ol>\r\n <li>The minimum OS\/390 release is now 2.10<\/li>\r\n <li>Contains all the maintenance items from version 2.0&nbsp; (2.0.1 through 2.0.36)<\/li>\r\n <li>Provides ability to choose 'OUTPUT' or 'HELD' JES queues when archived reports are sent back to the JES output queue.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<\/li>\r\n <li>&nbsp;Provides ability to send archived reports back to the JES output queue.<br>\r\n &nbsp;New required keyword for use in $WEB member:<br>\r\n WEBPAGE_ARCH2JES_CLASS&<\/li>\r\n <li>Provides ability to use wildcards '*' with the keyword:<br>\r\n JES_REPORT_SELECT_PROGRAMMER_NAME JES_REPORT_SELECT_PROGRAMMER_NAME_DEFAULT<\/li>\r\n <li>Provides ability to submit JCL from the 'History Directory' web page to restore a document from backup.<br>\r\n &nbsp;New keywords:<br>\r\n ARCHIVE_RESTORE_JCL_JOBCARD1 - Required keyword.<br>\r\n 3.3.27 ARCHIVE_RESTORE_JCL_JOBCARD1<br>\r\n ARCHIVE_RESTORE_JCL_JOBCARD2 - Required keyword.<br>\r\n 3.3.28 ARCHIVE_RESTORE_JCL_JOBCARD2<br>\r\n ARCHIVE_RESTORE_JCL_TAPE_UNIT - Optional keyword.<br>\r\n 3.3.29 ARCHIVE_RESTORE_JCL_TAPE_UNIT<br>\r\n ARCHIVE_RESTORE_JCL_DASD_UNIT - Optional keyword<br>\r\n 3.3.26 ARCHIVE_RESTORE_JCL_DASD_UNIT<\/li>\r\n <li>Provides control over report separator pages within a report segment.<br>\r\n New keywords:<br>\r\n SEGMENT_OVERRIDE_REPORT_SEPARATOR_PAGE<br>\r\n SEGMENT_OVERRIDE_REPORT_SEPARATOR_USERID<\/li>\r\n <li>Removes JES LRECL restriction of 4060. \r\n <ol style=\"list-style-type: lower-alpha;\">\r\n  <li>There will no longer be any restriction on JES LRECL.&nbsp;&nbsp;<\/li>\r\n  <li>Improved use of buffering will also improve performance on document deliveries.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<\/li>\r\n <\/ol>\r\n <\/li>\r\n <li>New keyword (REQUIRED):<br>\r\n JES_READ_BUFFER_SIZE<\/li>\r\n <li>Changed keywords:<br>\r\n TRANSMIT_BUFFER_SIZE -<br>\r\n changed maximum value from 32736 to 32767.<br>\r\n JES_REPORT_SIGNIFICANT_LRECL -<br>\r\n changed maximum value from 4060 to 32760.&nbsp;&nbsp;&nbsp;<\/li>\r\n <li>Batch Utility Changes.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>\r\n Adds ability to COPY or MOVE reports from one archive group to another.<br>\r\n Adds ability to specify any archive report group as a 'target' for a restore from backup. Previously there was no control, it restored to the original archive group.<br>\r\n Adds new valid value:<br>\r\n FUNCTION=COPY_TO_GROUP.<br>\r\n Adds new valid value:<br>\r\n FUNCTION=MOVE_TO_GROUP.<br>\r\n New keyword:<br>\r\n OVERLAY_DUPLICATE_REPORT.<br>\r\n New keyword:<br>\r\n SELECT_ONLY_BEGINING_GROUP<br>\r\n New keyword:<br>\r\n TARGET_REPORT_GROUP<\/li>\r\n <li>Added new JES report selection criteria.<br>\r\n Adds keyword: JES_REPORT_SELECT_ACCOUNTING_FIELD<br>\r\n Adds keyword: JES_REPORT_SELECT_ACCOUNTING_FIELD_DEFAULT<br>\r\n Adds keyword:<br>\r\n JES_REPORT_SELECT_ORIGIN_NODE<br>\r\n Adds keyword: JES_REPORT_SELECT_ORIGIN_NODE_DEFAULT<br>\r\n Adds keyword:<br>\r\n JES_REPORT_SELECT_PRIORITY<br>\r\n Adds keyword:<br>\r\n JES_REPORT_SELECT_PRIORITY_DEFAULT<br>\r\n Adds keyword: JES_REPORT_SELECT_PROGRAMMER_NAME<br>\r\n Adds keyword: JES_REPORT_SELECT_PROGRAMMER_NAME_DEFAULT<\/li>\r\n <li>Increases the maximum value of MAX_NUMBER_INTERNAL_TASKS from 512 to 1024.<\/li>\r\n <li>Provides ablity to reque a report to a NULL WRITER id.<br>\r\n You can now specify JES_REPORT_REQUE_WRITER=****; which will set the WRITER id to NULL.<\/li>\r\n <li>Added ability to control the format of the FTP server command PORT.<br>\r\n Added new keywords:<br>\r\n FTP_PORT_COMMAND_FORMAT<br>\r\n FTP_PORT_COMMAND_FORMAT_DEFAULT&nbsp;&nbsp; (REQUIRED)<\/li>\r\n <li>Added ability to specify a 'COPIES=' type parameter for DELIVERYTYPE=JES deliveries.<br>\r\n Adds new keyword:<br>\r\n JESDELIVERY_COPIES<\/li>\r\n<\/ol>","released_on":"2005-10-21T14:42:55.000000Z","deleted_at":null,"children":[]},{"id":185,"parent_id":null,"product_id":16,"release":"2.0","notes":"\n<p><strong>1. Functionality that added to JRB 1.1 by fixes (maintenance) are not listed here.<\/strong><br \/>\nNew keywords have been added that affect the appearance of the Archive Group Tree web page.\u00a0 They are all in support of the new ability to define multiple archive group trees (REPORT_GROUP_BEGIN_A_TREE)<\/p>\n<ul>\n <li>WEBPAGE_PREVIOUS_TREE_ICON - New optional keyword to specify a graphics file name to be used as an ICON.\u00a0 It will be used as a link to a previous tree.\u00a0<\/li>\n <li>WEBPAGE_PREVIOUS_TREE_TEXT - New Required keyword to specify the text associated with a link to a previous tree.<\/li>\n <li>WEBPAGE_TOP_TREE_ICON - New optional keyword to specify a graphics file name to be used as an ICON.\u00a0 It will be associated with the 'top tree' (the first tree defined in $GROUPS).<\/li>\n <li>WEBPAGE_TOP_TREE_TEXT - New required keyword to specify the text associated with the 'top tree' (the first tree defined in $GROUPS<\/li>\n <li>REPORT_GROUP_ICON - New optional keyword to specify the name of a graphics file that will be associated with a report group.<\/li>\n<\/ul>\n<p>\u00a0<\/p>\n<p><strong>2. New optional keyword REPORT_GROUP_BEGIN_A_TREE for the $GROUPS member provides the ability to define multiple report group trees.\u00a0<\/strong> <br \/>\nPreviously only one report group tree was supported.\u00a0 Customers that had many thousand report groups had no choice but to put all the groups under a single tree.\u00a0 Now an unlimited number of trees can be be defined.\u00a0 This provides better organization and a more focused, manageable number of report groups shown in the Archive Report Group Tree web page.<\/p>\n<p><strong>3. The Sign-on web page now optionally includes a pop-up window where you can place instructions, disclaimers or a greeting.\u00a0<\/strong><br \/>\nNew keywords shown below:<\/p>\n<ul>\n <li>WEBPAGE_SIGNON_POPUP_HEADING - Provide text for the heading of the pop-up.<\/li>\n <li>WEBPAGE_SIGNON_POPUP_MSG - Provide text, html or graphics for the body of the pop-up.<\/li>\n<\/ul>\n<p>\u00a0<\/p>\n<p><strong>4. New keyword SYSLOG_MESSAGE_LEVEL Controls which JRB messages are sent to the system log.<\/strong><\/p>\n<p><strong>5. JRB can now optionally generate a separator page during document delivery.\u00a0<\/strong><br \/>\nThe new keywords are listed below:<\/p>\n<ul>\n <li>REPORT_SEPARATOR_PAGE - Request separator page and position.<\/li>\n <li>REPORT_SEPARATOR_USERID - Userid to be optinally included on the separator page.<\/li>\n <li>REPORT_SEPARATOR_PAGE_DEFAULT -\u00a0 Request separator page and position<\/li>\n <li>REPORT_SEPARATOR_USERID_DEFAULT - Userid to be optionally included on the separator page.<\/li>\n<\/ul>\n<p>\u00a0<\/p>\n<p><strong>6. New substitution variables have been added.\u00a0 The old substitution variables dealing with time\/date were all on GMT.\u00a0<\/strong> <br \/>\nNew local time\/date substitution variables have been added:<\/p>\n<ul>\n <li>&LJBRUNDATE - LOCAL Date the report was created in the format mm-dd-yyyy<\/li>\n <li>&LJULJDAT -\u00a0 LOCAL current date in julian format: yyyy.ddd<\/li>\n <li>&LJM - LOCAL Month the report was created.\u00a0 Format: mm.<\/li>\n <li>&LJD - LOCAL Day the report was created.\u00a0 Format: dd.<\/li>\n <li>&LJYR - LOCAL Year the report was created.\u00a0 Format: yyyy.<\/li>\n <li>&LJOBTIME - LOCAL Time the report was created in the format hh.mm.ss<\/li>\n <li>&LJH - LOCAL Hour the report was created in the format hh.h)\u00a0 &LHN - LOCAL Minutes the report was created in the format mm.<\/li>\n <li>&LHS - LOCAL Seconds the report was created in the format ss<\/li>\n<\/ul>\n<p>\u00a0<\/p>\n<p><strong>7. DELIVERYTYPE=JES now 'carries forward' the FCB of the original output to the new output.<\/strong><\/p>\n<p><strong>8. During startup JRB now checks for the correct version and maintenance level of HTML, JAVASCRIPT and LOADLIB. (LOADLIB had previously been checked for correct version only.\u00a0<\/strong><\/p>\n<p><strong>9. On the Report Group Tree web page the action taken when clicked has changed.\u00a0<\/strong> Clicking the group name previously expanded the group then displayed the Report Directory page.\u00a0 Now clicking the group name (or ICON) will NOT expand the group, instead it will immediately display the Report Directory page<\/p>\n<p><strong>10. On the Archive Group Directory web page the status now scrolls to attract attention:<\/strong><\/p>\n<p>\"Left click to view report. Right click to download\/save report\". Also added a mouse over function that pops up a small title \"Left click to view report. Right click to download\/save report\" when the mouse is pointed at a document.<\/p>\n<p><strong>11. New keyword DELIVERY_MAX_LINES_PER_PAGE and DELIVERY_MAX_LINES_PER_PAGE_DEFAULT replaces obsolete keyword DELIVERY_CONVERSION_LINES_PER_PAGE.\u00a0<\/strong>The obsolete keyword was effective only for PDF conversion.\u00a0 <span style=\"display: none;\">\u00a0<\/span>The new keyword is effective for PDF conversion and most carriage control emulations.<\/p>\n<p><strong>12. The actions of some values of the DELIVERY_CC_EMULATION keyword have been changed.<\/strong><\/p>\n<p><strong>13. Forces top-of-page at the beginning of each JES output dataset<br \/>\n<\/strong><\/p>\n<p><strong>14. Adds carriage control (top-of-page) to output datasets that do not have carriage control.\u00a0<\/strong> Controlled by the keyword DELIVERY_MAX_LINES_PER_PAGE<\/p>\n<p><strong>15. New value 'IMPROVED_PASSTHRU' for keyword DELIVERY_CC_EMULATION.<\/strong><br \/>\nDELIVERY_CONVERSION=PDF<br \/>\nnow requires<br \/>\nDELIVERY_CC_EMULATION=IMPROVED_PASSTHRU<\/p>\n<p><strong>16. The keyword EXTERNAL_SECURITY has been changed from optional to required.<\/strong> Most customers will already have this keyword coded<\/p>\n<p><strong>17. Added a new flavor of TRACE command.\u00a0<\/strong>TRACE CC<\/p>\n<p><strong>18. The keyword DELIVERY_CONVERSION_LINES_PER_PAGE is obsolete.\u00a0<\/strong>JRB will automatically change this keyword wherever it is coded to the new keyword DELIVERY_MAX_LINES_PER_PAGE.<\/p>\n<p><strong>19. The install procedure no longer requires IBM's DFDSS to restore a dump of the HFS.\u00a0<\/strong> Components<br \/>\nof the HFS are now shipped in PDS's and copied into the HFS.<\/p>\n<p><strong>20. New section in this manual that graphically shows the areas in the web page where keywords can be used to customize the appearance<\/strong><\/p>\n<p><strong>21. The maximum LRECL for the JRB CONTROL PDS is now 1000 (was 255).<\/strong><\/p>\n<p><strong>22. In addition to the changes above approximately 50 other refinements and fixes were added.<\/strong><\/p>\n","released_on":"2005-01-07T23:21:25.000000Z","deleted_at":null,"children":[]},{"id":448,"parent_id":null,"product_id":16,"release":"- FIXES","notes":"\n<p><strong>IBM PTF'S REQUIRED<\/strong><\/p>\n<p><strong>Z\/OS 1.1<\/strong><\/p>\n<ol>\n <li>PTF UA55442 or Hyper APAR OA33407 - This is a sapi performance issue.<br \/>\n \u00a0<\/li>\n<\/ol>\n<p><strong>z\/OS 1.9 (r740)<\/strong><\/p>\n<ol>\n <li>\u00a0PTF UK25771 APAR PK42556<\/li>\n <li>\u00a0PTF UK27525 APAR PK46030<\/li>\n<\/ol>\n<p><br \/>\n<strong>z\/OS 1.8 (r730)\u00a0<\/strong><\/p>\n<ol>\n <li>PTF UK46253 APAR PK84073<\/li>\n <li>PTF UK27524 APAR PK46030<\/li>\n<\/ol>\n<p><br \/>\n<strong>z\/OS 1.7 (r720)\u00a0<\/strong> (and below)<\/p>\n<ol>\n <li>The following comments includes Z\/os 1.7 and below.<br \/>\n <br \/>\n There is a problem with HFS making this release of JRB incompatible with these releases if archival is used.\u00a0 IBM fixes are not available because these releases of z\/os are out of service.<br \/>\n <br \/>\n These APAR's deal with an IBM problem during 'chasing' the entries in an HFS\/ZFS directory. This problem only exists with large (>512 entries) structures so it is possible to have JRB archival at this level of z\/OS if the size of the archival is kept below the maximum of 512 entries.<br \/>\n \u00a0<\/li>\n <li>PTF UK27523 APAR PK46030<\/li>\n<\/ol>\n","released_on":"2011-01-01T23:21:25.000000Z","deleted_at":null,"children":[]}],"releases":[{"id":170,"parent_id":null,"product_id":16,"release":"2.4","notes":"\n<ol>\n <li>You can now specify the sensitivity level of an EMAIL.<br \/>\n EMAIL_SECURITY_SENSITIVITY_DEFAULT<br \/>\n EMAIL_SECURITY_SENSITIVITY<br \/>\n SEGMENT_OVERRIDE_EMAIL_SECURITY_SENSITIVITY<\/li>\n <li>Ability to control the colors of the hyperlinks to documents on the report directory web page.<br \/>\n A link also now changes color after you have visited that document.<br \/>\n New required keywords:<br \/>\n WEBPAGE_REPORTDIR_UNVISIT_LINK_COLOR<br \/>\n WEBPAGE_REPORTDIR_VISIT_LINK_COLOR<\/li>\n <li>Can now display number of records in a document on the report directory web page.<br \/>\n New valid parameter for keyword WEBPAGE_REPORTDIR_COLUMN_NAME<\/li>\n <li>You can now use any size picture file for the web screen banner, or have no banner at all.<br \/>\n Previously the banner file specified by the keyword WEB_BANNER_FILENAME had to be 450x90<br \/>\n pixels. Now you can specify a picture file of ANY size. If you do not want a banner picture at all you<br \/>\n can now specify 'none'.<br \/>\n WEB_BANNER_FILENAME<\/li>\n <li>You can now control the background color of the web pages.<br \/>\n New required keyword WEBPAGE_BG_COLOR.<\/li>\n <li>Ability to turn off the scrolling effect on the status line of the report directory web page.<br \/>\n New required $WEB keyword WEBPAGE_REPORTDIR_SCROLL_STATUS.<\/li>\n <li>A change to the 'Send report to JES' popup window.<br \/>\n It now displays the 'OK' button first, then the 'Cancel' button to be consistent with other popup windows.<\/li>\n<\/ol>\n","released_on":"2008-01-22T23:21:25.000000Z","deleted_at":null,"children":[]},{"id":182,"parent_id":null,"product_id":16,"release":"2.3","notes":"\n<ol>\n <li>All maintenance available for 2.2 has been applied to 2.3.<br \/>\n JRB 2.2.01 - JRB 2.2.46 have been applied.<br \/>\n \u00a0<\/li>\n <li>You now have control of the number of route entries delivering simultaneously. New keywords for $INIT: \n <ul>\n  <li>DELIVERY_TCLASS_DEFAULT -<br \/>\n  default TCLASS for deliveries.\u00a0 (required keyword)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS1 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS2 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS3 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS4 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n  <li>DELIVERY_TCLASS_MAXACT_CLASS5 -<br \/>\n  concurrent deliveries for this class.\u00a0 (required)<\/li>\n <\/ul>\n <\/li>\n <li>New keywords for route entries:<br \/>\n DELIVERY_TCLASS - sets TCLASS for a specific route entry.<br \/>\n \u00a0<\/li>\n <li>The above keywords implements a maximum active number of tasks in each of five classes.\u00a0 To implement: \n <ul>\n  <li>Decide how many route entries you want to allow for each TCLASS.<\/li>\n  <li>Specify the TCLASS for each route entry.<br \/>\n  You can use a combination of.<br \/>\n  DELIVERY_TCLASS_DEFAULT<br \/>\n  DELIVERY_TCLASS\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n  TCLASS has no effect on priority.... There are other keywords for that.\u00a0 It simply controls the maximum number of concurrently delivering route entries in a given TCLASS.<\/li>\n  <li>Drastic reduction in resource usage.<br \/>\n  <br \/>\n  <span style=\"display: none;\">\u00a0<\/span><\/li>\n <\/ul>\n <\/li>\n <li>Changes have been made to the internal task dispatcher.\u00a0 Previous versions maintained an internal JRB task for each route entry started.\u00a0 This version will require an internal JRB task ONLY when a particular route entry is actually delivering.\u00a0 This will result in a drastic reduction in the numbers of internal tasks, and their buffers, required for a given throughput.\u00a0 The bottom line will be a much leaner JRB.\u00a0 The real storage needed for a given amount of throughput will drop dramatically. This will show up in the following: \n <ul>\n  <li>Smaller real storage demands for JRB<\/li>\n  <li>Smaller value for MAX_NUMBER_INTERNAL_TASKS<\/li>\n  <li>Smaller value for 2K_BUFFERS<\/li>\n  <li>Smaller numbers of transmit buffers allocated.<\/li>\n  <li>Smaller number of JES read buffers<br \/>\n  \u00a0<\/li>\n <\/ul>\n <\/li>\n <li>These changes will show up on your z\/OS monitor (or SDSF) and the values reported by the SHOW command.\u00a0 Also it will show up in the tasks reported by the DISPLAYTASK command (compared to previous versions).<\/li>\n<\/ol>\n<p>\u00a0<\/p>\n<p>The following changes were implemented by maintenance items in JRB 2.3 and carried forward to JRB 2.4<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.26<br \/>\n===========<\/p>\n<ol>\n <li>Provides the ability to specify a codepage to be used when converting a document from EBCDIC to<br \/>\n ASCII.<br \/>\n New (required) keyword:<br \/>\n ASCII_CODEPAGE_DEFAULT<\/li>\n <li>Provides a new, optional, customizable message issued at delivery time.<br \/>\n New keyword:<br \/>\n DELIVERY_MSG_E422_DEFAULT<br \/>\n DELIVERY_MSG_E422<\/li>\n<\/ol>\n<p><br \/>\n===========<br \/>\nMAINT 2.3.26<br \/>\n===========<\/p>\n<p>Provides an extension to the INLINECNTL feature added in maint 2.3.24. You now have control of the processing that occurs if the value of the substitution variable &IC is NOT captured from an INLINECNTL record imbedded in the document to be delivered.<br \/>\n<br \/>\nNew keywords:<br \/>\nINLINECNTL_FIELD_DEFAULT_VALUE<br \/>\nINLINECNTL_FIELD_FAIL<\/p>\n<p>The keyword REPORT_SEPARATOR_USERID can now include any of the supported substitution variables.<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.24<br \/>\n===========<br \/>\nProvides the ability to specify a 'control' record that is imbedded in the report to be delivered. These control<br \/>\nrecords can specify delivery parameters and influence the way the report is delivered and split up.<br \/>\nNew keywords:<br \/>\nINLINECNTL_FIELD_COLUMN<br \/>\nINLINECNTL_FIELD_LENGTH<br \/>\nINLINECNTL_FIELD_TYPE<br \/>\nINLINECNTL_NAME<br \/>\nINLINECNTL_SEARCH_COLUMN<br \/>\nINLINECNTL_TEXT<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.21<br \/>\n===========<br \/>\nAdds a new FUNCTION called FIND_STRANDED_GROUPS to the JRBMUTIL batch utility program.<br \/>\n<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.20<br \/>\n===========<br \/>\nAdded support for mixed-case passwords on the web signon page with a new required keyword,<br \/>\nWEBPAGE_PASSWORD_CASE_SENSITIVE.<br \/>\n<br \/>\n===========<br \/>\nMAINT 2.3.19<br \/>\n===========<br \/>\nAdded the capability to select reports from the Held queue via the following new keywords:<br \/>\nJES_REPORT_SELECT_QUEUE=HELD;<br \/>\nJES_REPORT_SELECT_QUEUE_DEFAULT=HELD;<br \/>\n<br \/>\nWhen these keyword(s) are not present then reports will be selected from the Output queue, which is the<br \/>\ndefault when neither HELD nor OUTPUT is specified.<br \/>\n===========<br \/>\n<br \/>\nMAINT 2.3.18<br \/>\n===========<br \/>\nAdded a new possible value to following keywords:<br \/>\nARCHIVE_DYNAM_GROUP_DISPLAY=BOTH_NAME_FIRST;<br \/>\n<br \/>\nREPORT_GROUP_TREE_DISPLAY=BOTH_NAME_FIRST;<br \/>\n<br \/>\nREPORT_GROUP_TREE_DISPLAY_DEFAULT=BOTH_NAME_FIRST;<br \/>\n<br \/>\nThis provides the ability to customize the report group tree web page to display the name of the group first, followed<br \/>\nby the description... separated by a dash ('-').<br \/>\n<br \/>\n=========<br \/>\nMAINT 2.3.13<br \/>\n=========<br \/>\nProvides support for new substitution variable &SP. A single space will be substituted in its place. The<br \/>\nsubstitution will take place AFTER the normal blank compression. It can be used to place a space in keywords<br \/>\nwhose values have all spaces normally compressed such as:<br \/>\nFTP_WORKING_DIRECTORY<br \/>\nFTP_CREATE_DIRECTORY<br \/>\n<br \/>\n=========<br \/>\nMAINT 2.3.10<br \/>\n=========<\/p>\n<p>Added support for the ROOM parameter from the OUTPUT JCL statement.<\/p>\n<ol>\n <li>WEBPAGE_REPORTDIR_COLUMN_NAME now accepts the value OUTPUT_ROOM. It adds a column to the report directory web page.<\/li>\n <li>WEBPAGE_REPORTFILT_FILTER_NAME now accepts the value OUTPUT_ROOM. It adds an option to use this value to filter the report directory web page.<\/li>\n <li>Support for the ROOM parameter was extended into the 'Send Report to JES' function from the report directory web page.<\/li>\n <li>New required keyword in the $WEB member. WEBPAGE_REPORTDIR_OUTPUT_ROOM_LEN<\/li>\n<\/ol>\n<p><br \/>\n=========<br \/>\nMAINT 2.3.06<br \/>\n=========<\/p>\n<ol>\n <li>Added ability to specify a variable in these keywords:<br \/>\n EMAIL_FROM<br \/>\n EMAIL_FROM_DEFAULT<\/li>\n <li>Changed message JRBE089. No provides a description of a delivery failure. Provides a short description of the return code in event of a delivery failure. Previously only a return code was provided.<\/li>\n <li>Fixed a problem with EMAIL_TO when a variable was used. The variable was effective to the extent that the email was sent to the correct address however the REPLY address still contained the raw variable (it had not been substituted with the value of the variable).<\/li>\n <li>New message JRBE409 that indicates the completion of a delivery.<\/li>\n<\/ol>\n<p><br \/>\n=========<br \/>\nMAINT 2.3.02<br \/>\n=========<br \/>\nAdded new substitution variable &ACCT(n).<br \/>\nAccounting Information fields from JOB card. n is the relative position of the parameter desired.<br \/>\nFor an example of its use see FTP_FILENAME<\/p>\n","released_on":"2007-02-07T23:21:25.000000Z","deleted_at":null,"children":[]},{"id":183,"parent_id":null,"product_id":16,"release":"2.2","notes":"\n<ol>\n <li>New keyword: SEGMENT_OVERRIDE_JESDELIVERY_COPIES<\/li>\n <li>New keyword: TCPIP_COMPUTER_ASSOCIATES.<br \/>\n Provides compatibility for those customers running CA\/ACCESS.<\/li>\n <li>All of the maintenance applied to JRB 2.1. They are listed below: \n <ol>\n  <li>Provides ability to optionally add a line (maximum 130 characters) to the separator page.<br \/>\n  New keywords:<br \/>\n  REPORT_SEPARATOR_TEXT_DEFAULT<br \/>\n  REPORT_SEPARATOR_TEXT<\/li>\n  <li>Provides ability to specify email addresses via JCL.<br \/>\n  New keywords:<br \/>\n  EMAIL_OBTAIN_ADDRESS_FROM_JCL<br \/>\n  EMAIL_OBTAIN_ADDRESS_FROM_JCL_DEFAULT<\/li>\n  <li>Provides ability to specify what IP address the web server listens to connects on.<br \/>\n  New keyword: WEB_IP@<\/li>\n  <li>Archive Group Dynamic Creation<br \/>\n  Provides ability for JRB to dynamically create new archive groups dynamically without manually defining them in the $GROUPS member.<br \/>\n  New keywords:<br \/>\n  ARCHIVE_DYNAM_GROUP_CAPABLE<br \/>\n  ARCHIVE_DYNAM_GROUP<br \/>\n  ARCHIVE_DYNAM_MOTHER_GROUP<\/li>\n  <li>Ability to split up reports using CONTROLBREAKS<br \/>\n  Define the location within a report that contains a field. Each time that field changes from one page to another a CONTROLBREAK will occur. The previous report segment will end and other will begin. This feature is especially powerful when used with Archive Group<br \/>\n  Dynamic Creation.<br \/>\n  New keywords:<br \/>\n  CONTROLBREAK_NAME<br \/>\n  CONTROLBREAK_BOUNDARY<br \/>\n  CONTROLBREAK_TEXT_COLUMN<br \/>\n  CONTROLBREAK_TEXT_LENGTH<br \/>\n  CONTROLBREAK_TEXT_LINE<\/li>\n  <li>Can use segmentation in conjunction with CONTROLBREAKS<br \/>\n  In order to select the section of a report that is applicable to a CONTROLBREAK, segmentation can be used in conjunction.<\/li>\n  <li>NEW variable &CB(n).<br \/>\n  Will be replaced with the report text value associated with CONTROLBREAK in relative position n within the route entry. It can be used in conjunction with CONTROLBREAKS and Archive Group Dynamic Creation to build the name of the new group being created. Can also be used in REPORT_NAME or any other field that supports variables.<\/li>\n  <li>NEW function for the JRB utility.<br \/>\n  FUNCTION=UPGRADE_OBSOLETE_KEYWORDS<br \/>\n  If JRB detects the use of an obsolete keyword upon startup it will issue the message JRBE381 and terminate. You can use this new function of the JRB utility to automatically upgrade your keywords to the correct format.<\/li>\n  <li>Restructured the manual. Split sections previously in section IV into their own sections.<br \/>\n  New keywords: SSL_FTP_CERTIFICATE_LABEL<br \/>\n  SSL_FTP_CERTIFICATE_LABEL_DEFAULT<\/li>\n  <li>Provides SSL Client authentication for FTP deliveries<br \/>\n  Optionally, FTP servers and require that clients provide a digital certificate.<br \/>\n  This change supports that requirement.<br \/>\n  New keywords: SSL_FTP_CERTIFICATE_LABEL<br \/>\n  SSL_FTP_CERTIFICATE_LABEL_DEFAULT<\/li>\n  <li>Manual sections dealing with SSL support have been re-organized and clarified.<\/li>\n  <li>Re-structured the Archive and History in HFS.<br \/>\n  As a result documents will now be shown on the web pages from newest to oldest.<br \/>\n  = I M P O R T A N T N O T E =<br \/>\n  BEFORE YOU BRING UP JRB you MUST run the batch utility using the new utility keyword FUNCTION=UPGRADE_ARCHIVE; Failure to do so will cause the archive to become unusable until the UPGRADE_ARCHIVE is run.<\/li>\n  <li>Change to ARCHIVE to JES.<br \/>\n  The confirmation pop-up window now provides the ability to specify the following characteristics of the report placed on JES: \n  <ul>\n   <li>OUTPUT CLASS<\/li>\n   <li>FORMID<\/li>\n   <li>DESTINATION<\/li>\n  <\/ul>\n  <\/li>\n  <li>Change to keywords<br \/>\n  JESDELIVERY_FORM<br \/>\n  JESDELIVERY_FORM_DEFAULT<br \/>\n  SEGMENT_OVERRIDE_JESDELIVERY_FORM<\/li>\n  <li>NEW DELIVERYTYPE=REQUE;<br \/>\n  This new deliverytype does not actually deliver a report, is simply changes the<br \/>\n  JES characteristics of a report. It does not create a new JES output like DELIVERTYPE=JES<br \/>\n  does, it just changes the characteristics of the original report.<br \/>\n  New keywords: JES_REPORT_REQUE_NODE_DESTID<br \/>\n  JES_REPORT_REQUE_NODE_DESTID_DEFAULT<\/li>\n  <li>DIRECTORY WEB PAGE FILTER WINDOW CHANGES:<br \/>\n  1. With multiple report directory windows open each one of them may now have a filter window associated with it. Previously only the first directory window could have a filter window.<br \/>\n  2. Removed the alert window that popped up when the 'FILTER OFF\" button was pressed.<br \/>\n  3. The 'FILTER OFF\" button is now 'grayed out' and disabled unless there is actually a filter window open.<br \/>\n  4. All filter fields now translate all input into upper case except for the 'PROGRAMMER NAME' field.<br \/>\n  5. The 'CREATION DATE TO\/FROM' fields initial values have changed: \n  <ul>\n   <li>The 'TO DATE' is now the date obtained from JRB, previously it was the date obtained from the workstation.<\/li>\n   <li>The 'FROM DATE' is now calculated from the 'TO DATE'.<br \/>\n   A number of days are subtracted from the 'TO DATE' to obtain the 'FROM DATE'. The number of days subtracted are obtained from:<br \/>\n   New keyword:<br \/>\n   WEBPAGE_REPORT_FILTER_FROM_DATE_OFFSET<span style=\"display: none;\">\u00a0<\/span><\/li>\n  <\/ul>\n  <\/li>\n  <li>New keywords:<br \/>\n  FTP_TCPIP_READ_TIMEOUT<br \/>\n  FTP_TCPIP_READ_TIMEOUT_DEFAULT<\/li>\n  <li>New option for keyword FTP_MODE and FTP_MODE_DEFAULT.<br \/>\n  You can now specify<br \/>\n  FTP_MODE=PASSIVE_POSTCONNECT<\/li>\n  <li>Changed the FTP protocol associated with FTP_MODE=PASSIVE;<br \/>\n  Some FTP servers were causing deliveries to hang up. Tracing revealed JRB waiting upon a TCP\/READ attempting to receive the response of a 'STOR' FTP command.<\/li>\n <\/ol>\n <\/li>\n<\/ol>\n<ul>\n <li>Previously JRB would: Issue 'PASV', Issue 'STOR', then connects to the server. (PASV,STOR,CONNECT) Now JRB will: Issue 'PASV', connect to the server, then Issue 'STOR'.(PASV,CONNECT,STOR)<\/li>\n <li>In order to preserve previous functionality that might be required from some servers FTP_MODE=PASSIVE_POSTCONNECT now will use the old protocol. (PASV,STOR,CONNECT)<\/li>\n<\/ul>\n","released_on":"2006-06-15T21:21:25.000000Z","deleted_at":null,"children":[]},{"id":184,"parent_id":null,"product_id":16,"release":"2.1","notes":"<ol>\r\n <li>The minimum OS\/390 release is now 2.10<\/li>\r\n <li>Contains all the maintenance items from version 2.0&nbsp; (2.0.1 through 2.0.36)<\/li>\r\n <li>Provides ability to choose 'OUTPUT' or 'HELD' JES queues when archived reports are sent back to the JES output queue.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<\/li>\r\n <li>&nbsp;Provides ability to send archived reports back to the JES output queue.<br>\r\n &nbsp;New required keyword for use in $WEB member:<br>\r\n WEBPAGE_ARCH2JES_CLASS&<\/li>\r\n <li>Provides ability to use wildcards '*' with the keyword:<br>\r\n JES_REPORT_SELECT_PROGRAMMER_NAME JES_REPORT_SELECT_PROGRAMMER_NAME_DEFAULT<\/li>\r\n <li>Provides ability to submit JCL from the 'History Directory' web page to restore a document from backup.<br>\r\n &nbsp;New keywords:<br>\r\n ARCHIVE_RESTORE_JCL_JOBCARD1 - Required keyword.<br>\r\n 3.3.27 ARCHIVE_RESTORE_JCL_JOBCARD1<br>\r\n ARCHIVE_RESTORE_JCL_JOBCARD2 - Required keyword.<br>\r\n 3.3.28 ARCHIVE_RESTORE_JCL_JOBCARD2<br>\r\n ARCHIVE_RESTORE_JCL_TAPE_UNIT - Optional keyword.<br>\r\n 3.3.29 ARCHIVE_RESTORE_JCL_TAPE_UNIT<br>\r\n ARCHIVE_RESTORE_JCL_DASD_UNIT - Optional keyword<br>\r\n 3.3.26 ARCHIVE_RESTORE_JCL_DASD_UNIT<\/li>\r\n <li>Provides control over report separator pages within a report segment.<br>\r\n New keywords:<br>\r\n SEGMENT_OVERRIDE_REPORT_SEPARATOR_PAGE<br>\r\n SEGMENT_OVERRIDE_REPORT_SEPARATOR_USERID<\/li>\r\n <li>Removes JES LRECL restriction of 4060. \r\n <ol style=\"list-style-type: lower-alpha;\">\r\n  <li>There will no longer be any restriction on JES LRECL.&nbsp;&nbsp;<\/li>\r\n  <li>Improved use of buffering will also improve performance on document deliveries.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<\/li>\r\n <\/ol>\r\n <\/li>\r\n <li>New keyword (REQUIRED):<br>\r\n JES_READ_BUFFER_SIZE<\/li>\r\n <li>Changed keywords:<br>\r\n TRANSMIT_BUFFER_SIZE -<br>\r\n changed maximum value from 32736 to 32767.<br>\r\n JES_REPORT_SIGNIFICANT_LRECL -<br>\r\n changed maximum value from 4060 to 32760.&nbsp;&nbsp;&nbsp;<\/li>\r\n <li>Batch Utility Changes.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br>\r\n Adds ability to COPY or MOVE reports from one archive group to another.<br>\r\n Adds ability to specify any archive report group as a 'target' for a restore from backup. Previously there was no control, it restored to the original archive group.<br>\r\n Adds new valid value:<br>\r\n FUNCTION=COPY_TO_GROUP.<br>\r\n Adds new valid value:<br>\r\n FUNCTION=MOVE_TO_GROUP.<br>\r\n New keyword:<br>\r\n OVERLAY_DUPLICATE_REPORT.<br>\r\n New keyword:<br>\r\n SELECT_ONLY_BEGINING_GROUP<br>\r\n New keyword:<br>\r\n TARGET_REPORT_GROUP<\/li>\r\n <li>Added new JES report selection criteria.<br>\r\n Adds keyword: JES_REPORT_SELECT_ACCOUNTING_FIELD<br>\r\n Adds keyword: JES_REPORT_SELECT_ACCOUNTING_FIELD_DEFAULT<br>\r\n Adds keyword:<br>\r\n JES_REPORT_SELECT_ORIGIN_NODE<br>\r\n Adds keyword: JES_REPORT_SELECT_ORIGIN_NODE_DEFAULT<br>\r\n Adds keyword:<br>\r\n JES_REPORT_SELECT_PRIORITY<br>\r\n Adds keyword:<br>\r\n JES_REPORT_SELECT_PRIORITY_DEFAULT<br>\r\n Adds keyword: JES_REPORT_SELECT_PROGRAMMER_NAME<br>\r\n Adds keyword: JES_REPORT_SELECT_PROGRAMMER_NAME_DEFAULT<\/li>\r\n <li>Increases the maximum value of MAX_NUMBER_INTERNAL_TASKS from 512 to 1024.<\/li>\r\n <li>Provides ablity to reque a report to a NULL WRITER id.<br>\r\n You can now specify JES_REPORT_REQUE_WRITER=****; which will set the WRITER id to NULL.<\/li>\r\n <li>Added ability to control the format of the FTP server command PORT.<br>\r\n Added new keywords:<br>\r\n FTP_PORT_COMMAND_FORMAT<br>\r\n FTP_PORT_COMMAND_FORMAT_DEFAULT&nbsp;&nbsp; (REQUIRED)<\/li>\r\n <li>Added ability to specify a 'COPIES=' type parameter for DELIVERYTYPE=JES deliveries.<br>\r\n Adds new keyword:<br>\r\n JESDELIVERY_COPIES<\/li>\r\n<\/ol>","released_on":"2005-10-21T14:42:55.000000Z","deleted_at":null,"children":[]},{"id":185,"parent_id":null,"product_id":16,"release":"2.0","notes":"\n<p><strong>1. Functionality that added to JRB 1.1 by fixes (maintenance) are not listed here.<\/strong><br \/>\nNew keywords have been added that affect the appearance of the Archive Group Tree web page.\u00a0 They are all in support of the new ability to define multiple archive group trees (REPORT_GROUP_BEGIN_A_TREE)<\/p>\n<ul>\n <li>WEBPAGE_PREVIOUS_TREE_ICON - New optional keyword to specify a graphics file name to be used as an ICON.\u00a0 It will be used as a link to a previous tree.\u00a0<\/li>\n <li>WEBPAGE_PREVIOUS_TREE_TEXT - New Required keyword to specify the text associated with a link to a previous tree.<\/li>\n <li>WEBPAGE_TOP_TREE_ICON - New optional keyword to specify a graphics file name to be used as an ICON.\u00a0 It will be associated with the 'top tree' (the first tree defined in $GROUPS).<\/li>\n <li>WEBPAGE_TOP_TREE_TEXT - New required keyword to specify the text associated with the 'top tree' (the first tree defined in $GROUPS<\/li>\n <li>REPORT_GROUP_ICON - New optional keyword to specify the name of a graphics file that will be associated with a report group.<\/li>\n<\/ul>\n<p>\u00a0<\/p>\n<p><strong>2. New optional keyword REPORT_GROUP_BEGIN_A_TREE for the $GROUPS member provides the ability to define multiple report group trees.\u00a0<\/strong> <br \/>\nPreviously only one report group tree was supported.\u00a0 Customers that had many thousand report groups had no choice but to put all the groups under a single tree.\u00a0 Now an unlimited number of trees can be be defined.\u00a0 This provides better organization and a more focused, manageable number of report groups shown in the Archive Report Group Tree web page.<\/p>\n<p><strong>3. The Sign-on web page now optionally includes a pop-up window where you can place instructions, disclaimers or a greeting.\u00a0<\/strong><br \/>\nNew keywords shown below:<\/p>\n<ul>\n <li>WEBPAGE_SIGNON_POPUP_HEADING - Provide text for the heading of the pop-up.<\/li>\n <li>WEBPAGE_SIGNON_POPUP_MSG - Provide text, html or graphics for the body of the pop-up.<\/li>\n<\/ul>\n<p>\u00a0<\/p>\n<p><strong>4. New keyword SYSLOG_MESSAGE_LEVEL Controls which JRB messages are sent to the system log.<\/strong><\/p>\n<p><strong>5. JRB can now optionally generate a separator page during document delivery.\u00a0<\/strong><br \/>\nThe new keywords are listed below:<\/p>\n<ul>\n <li>REPORT_SEPARATOR_PAGE - Request separator page and position.<\/li>\n <li>REPORT_SEPARATOR_USERID - Userid to be optinally included on the separator page.<\/li>\n <li>REPORT_SEPARATOR_PAGE_DEFAULT -\u00a0 Request separator page and position<\/li>\n <li>REPORT_SEPARATOR_USERID_DEFAULT - Userid to be optionally included on the separator page.<\/li>\n<\/ul>\n<p>\u00a0<\/p>\n<p><strong>6. New substitution variables have been added.\u00a0 The old substitution variables dealing with time\/date were all on GMT.\u00a0<\/strong> <br \/>\nNew local time\/date substitution variables have been added:<\/p>\n<ul>\n <li>&LJBRUNDATE - LOCAL Date the report was created in the format mm-dd-yyyy<\/li>\n <li>&LJULJDAT -\u00a0 LOCAL current date in julian format: yyyy.ddd<\/li>\n <li>&LJM - LOCAL Month the report was created.\u00a0 Format: mm.<\/li>\n <li>&LJD - LOCAL Day the report was created.\u00a0 Format: dd.<\/li>\n <li>&LJYR - LOCAL Year the report was created.\u00a0 Format: yyyy.<\/li>\n <li>&LJOBTIME - LOCAL Time the report was created in the format hh.mm.ss<\/li>\n <li>&LJH - LOCAL Hour the report was created in the format hh.h)\u00a0 &LHN - LOCAL Minutes the report was created in the format mm.<\/li>\n <li>&LHS - LOCAL Seconds the report was created in the format ss<\/li>\n<\/ul>\n<p>\u00a0<\/p>\n<p><strong>7. DELIVERYTYPE=JES now 'carries forward' the FCB of the original output to the new output.<\/strong><\/p>\n<p><strong>8. During startup JRB now checks for the correct version and maintenance level of HTML, JAVASCRIPT and LOADLIB. (LOADLIB had previously been checked for correct version only.\u00a0<\/strong><\/p>\n<p><strong>9. On the Report Group Tree web page the action taken when clicked has changed.\u00a0<\/strong> Clicking the group name previously expanded the group then displayed the Report Directory page.\u00a0 Now clicking the group name (or ICON) will NOT expand the group, instead it will immediately display the Report Directory page<\/p>\n<p><strong>10. On the Archive Group Directory web page the status now scrolls to attract attention:<\/strong><\/p>\n<p>\"Left click to view report. Right click to download\/save report\". Also added a mouse over function that pops up a small title \"Left click to view report. Right click to download\/save report\" when the mouse is pointed at a document.<\/p>\n<p><strong>11. New keyword DELIVERY_MAX_LINES_PER_PAGE and DELIVERY_MAX_LINES_PER_PAGE_DEFAULT replaces obsolete keyword DELIVERY_CONVERSION_LINES_PER_PAGE.\u00a0<\/strong>The obsolete keyword was effective only for PDF conversion.\u00a0 <span style=\"display: none;\">\u00a0<\/span>The new keyword is effective for PDF conversion and most carriage control emulations.<\/p>\n<p><strong>12. The actions of some values of the DELIVERY_CC_EMULATION keyword have been changed.<\/strong><\/p>\n<p><strong>13. Forces top-of-page at the beginning of each JES output dataset<br \/>\n<\/strong><\/p>\n<p><strong>14. Adds carriage control (top-of-page) to output datasets that do not have carriage control.\u00a0<\/strong> Controlled by the keyword DELIVERY_MAX_LINES_PER_PAGE<\/p>\n<p><strong>15. New value 'IMPROVED_PASSTHRU' for keyword DELIVERY_CC_EMULATION.<\/strong><br \/>\nDELIVERY_CONVERSION=PDF<br \/>\nnow requires<br \/>\nDELIVERY_CC_EMULATION=IMPROVED_PASSTHRU<\/p>\n<p><strong>16. The keyword EXTERNAL_SECURITY has been changed from optional to required.<\/strong> Most customers will already have this keyword coded<\/p>\n<p><strong>17. Added a new flavor of TRACE command.\u00a0<\/strong>TRACE CC<\/p>\n<p><strong>18. The keyword DELIVERY_CONVERSION_LINES_PER_PAGE is obsolete.\u00a0<\/strong>JRB will automatically change this keyword wherever it is coded to the new keyword DELIVERY_MAX_LINES_PER_PAGE.<\/p>\n<p><strong>19. The install procedure no longer requires IBM's DFDSS to restore a dump of the HFS.\u00a0<\/strong> Components<br \/>\nof the HFS are now shipped in PDS's and copied into the HFS.<\/p>\n<p><strong>20. New section in this manual that graphically shows the areas in the web page where keywords can be used to customize the appearance<\/strong><\/p>\n<p><strong>21. The maximum LRECL for the JRB CONTROL PDS is now 1000 (was 255).<\/strong><\/p>\n<p><strong>22. In addition to the changes above approximately 50 other refinements and fixes were added.<\/strong><\/p>\n","released_on":"2005-01-07T23:21:25.000000Z","deleted_at":null,"children":[]},{"id":283,"parent_id":null,"product_id":16,"release":"2.5","notes":"\n<ol>\n <li>All maintenance available for 2.4 has been applied to 2.5<\/li>\n <li>Required change to $INIT keyword LOCAL_HFS_ROOT<\/li>\n <li>Required change to $INIT keyword CONCURRENT_TCP_CONNECTS_PER_SUBTASK<\/li>\n <li>All C programs have been re-written to XPLINK C++ and the Language Environment has been re-written to use 'PIPI' interfaces.\u00a0 The bottom line is better performance and access to additional functionality.<\/li>\n <li>Archive Compression now available.<\/li>\n <li>New utility function to compress archive documents.<\/li>\n<\/ol>\n","released_on":"2009-05-13T21:21:25.000000Z","deleted_at":null,"children":[]},{"id":284,"parent_id":null,"product_id":16,"release":"3.0","notes":"\n<p>Added ability to process AFP (Advanced Function Printing) documents using MacKinney Systems Transform (MPT).\u00a0 With MPT, JRB can now transform AFP documents into PDF, PCL or Postscript. The resulting documents will contain all fonts, overlays, graphics and formatting of the original AFP document.\u00a0 When used with archiving, JRB can now render your AFP documents on your browser just as they would look printed.<\/p>\n","released_on":"2009-06-02T21:21:25.000000Z","deleted_at":null,"children":[{"id":328,"parent_id":284,"product_id":16,"release":"3.0.012","notes":"\n<ul>\n <li>Specify a document 'generation' limit for an archive group.<\/li>\n <li>Sets a return code if no documents are selected for backup.<\/li>\n <li>Adds keywords to exclude reports from selection from JES.<\/li>\n <li>Send any raw SITE commands to the FTP server using new keyword: FTP_QUOTE_COMMAND<\/li>\n <li>Specify unlimited number of email addresses (notify also).\u00a0<\/li>\n<\/ul>\n","released_on":"2009-09-04T21:21:25.000000Z","deleted_at":null}]},{"id":364,"parent_id":null,"product_id":16,"release":"3.1","notes":"\n<ul>\n <li>JES report selection now includes job return codes.<br \/>\n You can now select JES output based upon the success or failure of the job. This can be useful by segregating job output that 'failed'. You can also use email to notify that a job failed.<br \/>\n New keywords:<br \/>\n 11.2.208 JES_REPORT_SELECT_JOB_CONDITION<br \/>\n 11.2.215 JES_REPORT_SELECT_MAXRC_THRESHOLD<\/li>\n <li>New keywords:<br \/>\n Provides ability to override the number of days history is to be kept for a document segment.<br \/>\n 11.2.421 SEGMENT_OVERRIDE_HISTORY_DAYS_TO_RETAIN<br \/>\n 11.2.422 SEGMENT_OVERRIDE_HISTORY_DISPOSITION<\/li>\n <li>Increased maximum number of route entries to 12,000<\/li>\n <li>All 3.0 maintenance.<br \/>\n JRB 3.0.01 - JRB 3.0.15 have been applied.<\/li>\n<\/ul>\n","released_on":"2009-10-23T21:21:25.000000Z","deleted_at":null,"children":[{"id":386,"parent_id":364,"product_id":16,"release":"3.1.022","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2010-03-25T21:21:25.000000Z","deleted_at":null},{"id":382,"parent_id":364,"product_id":16,"release":"3.1.015","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2010-02-18T23:21:25.000000Z","deleted_at":null}]},{"id":403,"parent_id":null,"product_id":16,"release":"3.2","notes":"<p><strong>1. Added PAGESORT.<\/strong> Ability to sort document pages\nbased upon sort fields found in the document pages.<br>\nPick any number of \"fields\" within a page to sort on. JRB will sort the\ndocument pages based on the field(s) while performing a document\ndelivery.\u00a0<br>\n<em>Example:<\/em>\u00a0 Sort a document to bring all the pages for a\nparticular customer # together.<br>\n<br>\n<strong>2. Added ability to insert text (plain and AFP) into a document\nas it is being delivered.<\/strong><br>\nCan insert Plain text and AFP text into a document. Provides a range of\npossibilities from adding pages to inserting OMR (Optical Mark\nRecognition).<br>\n<em>Example:<\/em>\u00a0 Insert OMR marks into a document that can be\nread by a postage sorter\/stuffer to minimize postage costs.<br>\n\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0<br>\n<strong>3. Added ability to capture text fields on each\npage.<\/strong>Populate new substitution variable\n&TC(<em>n<\/em>).<br>\n<em>Example:<\/em> Capture a field on a page to be used as the email\naddress to deliver the page. .<br>\n<br>\n<strong>4.<\/strong> <strong>JRB can now Archive the following document\ntypes directly:\u00a0<br><\/strong>\n<strong>\u00a0\u00a0\u00a0\u00a0<\/strong><strong>.CSV<\/strong><br>\n<strong>\u00a0\u00a0\u00a0\u00a0<\/strong><strong>.PS<br><\/strong><strong>\u00a0\u00a0\u00a0\u00a0<\/strong><strong>.PCL<\/strong><br>\n<em>Example:\u00a0<\/em> You have a EXCEL file (comma delimited). You\ncan now archive it directly into JRB for access by your customers via a\nbrowser. Also supports POSTSCRIPT and Printer Control Language\ndocuments.<br>\n<br>\n<strong>5.<\/strong> <strong>Can now control the width and title of\ncolumns on the document directory webpage.<\/strong><br>\nCustomize your JRB web page document directory. You have always been\nable to pick the columns (Jobname, report name, date\/time, formid\u00a0\netc..) and the order in which they appear. Now you can specify the\ntitle of each column so it fits the needs of your user community. You\ncan also set the width (in pels) of each column.<br>\n<strong><br>\n6. On history restore window you can now specify max\/min\/default\ndays-to-retain.<\/strong><br>\nCustomize your JRB ARCHIVE web pages. When a user clicks on a history\ndocument to restore it they have always been presented with a window to\nspecify how many days the document will remain before expiration. Now\nthey are provided with a pulldown list of days.. the JRB administrator\ncan specify the min\/max days to retain that will be presented as well\nas the \"default\"\u00a0 number of days.<br>\n<br>\n<strong>7.<\/strong> <strong>All maintenance from JRB 3.1.\nHighlights:<\/strong><br>\n\u00a0\u00a0\u00a0 <em>a)<\/em> New webpage report directory\ncolumn-\u00a0 \"NUMBER of PAGES\"<br>\n\u00a0\u00a0\u00a0 <em>b)<\/em> Can now select document from JES based\non the \"transaction JOBNAME\"<br>\n\u00a0\u00a0\u00a0 <em>c)<\/em> New substitution variable &JCLTITL.\nFrom TITLE JCL parm.<\/p>\n","released_on":"2010-10-07T21:21:25.000000Z","deleted_at":null,"children":[{"id":456,"parent_id":403,"product_id":16,"release":"3.2.048","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2011-08-10T21:21:25.000000Z","deleted_at":null},{"id":413,"parent_id":403,"product_id":16,"release":"3.2.025","notes":"\n<p>\u00a0Maintenance release.<\/p>\n","released_on":"2011-01-10T23:21:25.000000Z","deleted_at":null},{"id":410,"parent_id":403,"product_id":16,"release":"3.2.023","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2010-12-15T23:21:25.000000Z","deleted_at":null}]},{"id":448,"parent_id":null,"product_id":16,"release":"- FIXES","notes":"\n<p><strong>IBM PTF'S REQUIRED<\/strong><\/p>\n<p><strong>Z\/OS 1.1<\/strong><\/p>\n<ol>\n <li>PTF UA55442 or Hyper APAR OA33407 - This is a sapi performance issue.<br \/>\n \u00a0<\/li>\n<\/ol>\n<p><strong>z\/OS 1.9 (r740)<\/strong><\/p>\n<ol>\n <li>\u00a0PTF UK25771 APAR PK42556<\/li>\n <li>\u00a0PTF UK27525 APAR PK46030<\/li>\n<\/ol>\n<p><br \/>\n<strong>z\/OS 1.8 (r730)\u00a0<\/strong><\/p>\n<ol>\n <li>PTF UK46253 APAR PK84073<\/li>\n <li>PTF UK27524 APAR PK46030<\/li>\n<\/ol>\n<p><br \/>\n<strong>z\/OS 1.7 (r720)\u00a0<\/strong> (and below)<\/p>\n<ol>\n <li>The following comments includes Z\/os 1.7 and below.<br \/>\n <br \/>\n There is a problem with HFS making this release of JRB incompatible with these releases if archival is used.\u00a0 IBM fixes are not available because these releases of z\/os are out of service.<br \/>\n <br \/>\n These APAR's deal with an IBM problem during 'chasing' the entries in an HFS\/ZFS directory. This problem only exists with large (>512 entries) structures so it is possible to have JRB archival at this level of z\/OS if the size of the archival is kept below the maximum of 512 entries.<br \/>\n \u00a0<\/li>\n <li>PTF UK27523 APAR PK46030<\/li>\n<\/ol>\n","released_on":"2011-01-01T23:21:25.000000Z","deleted_at":null,"children":[]},{"id":494,"parent_id":null,"product_id":16,"release":"3.3","notes":"\n<p><strong>1. All maintenance from JRB 3.2.\u00a0\u00a0<\/strong><br \/>\n<strong><br \/>\n2. Restructure Document Archive Access Providing Better Web Performance and Lower Overhead<\/strong><br \/>\nRestructures the code used to search for documents in the archive and history. It adds some overhead to JRB startup in exchange for much less (90% less) overhead during a document search. It does this by avoiding a C++ directory traverse whenever possible. It employs an HFS file to 'save' the results of a directory traverse. The\u00a0 HFS file is rebuilt whenever the following is true:<br \/>\na. JRB startup OR INSTALL$GROUP command is issued on the console.<br \/>\nAND<br \/>\nb. JRB detects the $GROUPS member has been updated since the last rebuild.\u00a0\u00a0\u00a0<br \/>\n<br \/>\n<strong>3. Added a Choice of REPORT_NODE_SCAN Intensity. Provides quicker JRB startup.(Also faster INSTALL$GROUP command execution)<\/strong> REPORT_NODE_SCAN=YES; in $INIT is now a \"QUICK\"scan. It uses the current directory traverse save file mentioned in item 2 above.REPORT_NODE_SCAN=DEEP; in $INIT is a more intense scan. It rebuilds the directory traverse save file. It is more accurate, but at a higher cost of overhead.<br \/>\n\u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\u00a0\u00a0<br \/>\n<strong>4. New Batch Utility FUNCTION=FIND_STRANDED_GROUPS_DEEP;<\/strong> FIND_STRANDED_GROUPS is now a \"quick\" scan. The DEEP scan is equal to the DEEP scan introduced in item 3 above.<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n<strong>5. Eliminated JRBSUB.<\/strong> Merged JRBSUB with JRBLOG<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n<strong>6. Enabled New Columns to be Displayable in the History Directory Web Page.<\/strong><br \/>\n<br \/>\nThe following columns were not being previous populated in the History Directory Web Page:<\/p>\n<ul>\n <li>ROOM<\/li>\n <li>PAGES_OR_RECS<\/li>\n <li>MAX_CC<\/li>\n <li>FCB<\/li>\n <li>NUM_RECORDS<\/li>\n <li>OUTPUT_DEPT<\/li>\n <li>OUTPUT_TITLE<\/li>\n <li>OUTPUT_NAME<\/li>\n <li>OUTPUT_ADDRESS<\/li>\n <li>EXECUTION_TIME<\/li>\n<\/ul>\n<p><br \/>\n<strong>7. Added ability to Exclude Selection of JES Output based upon DDNAME<\/strong><br \/>\n<strong><br \/>\n8. Removed carriage control requirement for TXT_CAPTURE_FIELD_TYPE=SEARCH.<\/strong><br \/>\nPreviously TXT_CAPTURE_FEILD_TYPE=SEARCH required that the JES output must have carriage control. Now if TXT_CAPTURE_TEXT_LINE=0;\u00a0 is in use the JES output is NOT required to have carriage control.<br \/>\n<strong><br \/>\n9. Web Page Change. The History Restore Dropdown Can Now Force the User to Specify an Expiration for the Document being Restored.<\/strong><br \/>\n<br \/>\nNew Valid Parameter Value for WEBPAGE_HISTORY_RESTORE_WINDOW. The new parameter \"EXPIREONLY\" causes the \"Keep Restored Document Indefinitely\" radio button to be greyed out and disabled.<br \/>\n<br \/>\n<strong>10. Obsolete keywords<\/strong><br \/>\nDELIVERYTYPE=SEQ; now determines the best LRECL dynamically so the following are obsolete:<br \/>\n<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 OFFLOAD_LRECL<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 OFFLOAD_LRECL_DEFAULT<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SEGMENT_OVERRIDE_OFFLOAD_LRECL<br \/>\n<br \/>\n<br \/>\n<strong>11. Keyword processing changes.<\/strong><br \/>\n<strong>a.\u00a0 Obsolete keywords are now automatically REPLACED\/REMOVED.<\/strong><br \/>\nAt JRB startup, obsolete keywords will automatically be replaced with a current keyword or removed. The JRB administrator will no longer be required to manually removed these keywords.<br \/>\n<br \/>\nExample messages:<\/p>\n<p><br \/>\n\u00a0 JRBE513 ** OBSOLETE KEYWORD, WILL BE DYNAMICALLY COMMETED OUT, SEE LOG\u00a0 **<br \/>\n\u00a0 JRBE059 ** ERROR ON LINE:151\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 MEMBER:$INIT\u00a0\u00a0\u00a0\u00a0\u00a0 **\u00a0<br \/>\n\u00a0 * OBSOLETE, COMMENTED OUT BY JRB: OFFLOAD_LRECL_DEFAULT=200;\u00a0\u00a0\u00a0\u00a0<br \/>\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n\u00a0JRBE529 ** OBSOLETE KEYWORD, WILL BE DYNAMICALLY REPLACED, SEE LOG **<br \/>\n\u00a0JRBE059 ** ERROR ON LINE:120\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 MEMBER:$INIT\u00a0\u00a0\u00a0\u00a0\u00a0 **\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/p>\n<p><br \/>\n<strong>b. Newly Introduced Required Keywords Are Now Automatically Added for you.<\/strong><br \/>\nWhen a new keyword is introduced it will no longer be required to manually add them.\u00a0 If a default can be determined the keyword will be automatically added at startup.<br \/>\n<br \/>\nExample messages:<br \/>\n\u00a0JRBE381 ** REQUIRED KEYWORD WILL BE DYNAMICALLY ADDED:512BYTE_BUFFERS<br \/>\n\u00a0JRBE530 ** KEYWORD ADDED TO MEMBER:$INIT\u00a0\u00a0\u00a0 RECORD #:175\u00a0\u00a0<br \/>\n* THE FOLLOWING RECORD WAS ADDED DYNAMICALLY BY JRB3.3\u00a0\u00a0 03\/29\/2012\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<br \/>\n<strong><br \/>\nc. UPGRADE_OBSOLETE_KEYWORDS\u00a0 Utility Function is now Obsolete.<\/strong><br \/>\nBecause of the new automatic keyword processing at JRB startup this function has been removed.<br \/>\n<strong><br \/>\n12. Optional SMF Record Written Upon Each Web Access of an Archived Document.<\/strong><br \/>\n<strong><br \/>\n13. Optional SMF Record Written Upon Successful FTP Delivery<\/strong><br \/>\n<strong>New Keyword<\/strong> SMF_FTP_DELIVERY_119<br \/>\nThis can be used for chargeback uses or audit trail.<br \/>\n<strong><br \/>\n14. Only One JRB With the Same Name Can be Running at the Same Time.<\/strong><br \/>\nAn attempt to bring up a 2nd JRB with the same name will result in the following message and JRB will terminate.:<br \/>\n\u00a0\u00a0\u00a0 JRBE507 ** A JRB WITH THIS PROCNAME IS ALREADY RUNNING **\u00a0\u00a0<br \/>\n<br \/>\n<strong>15. JRB Batch Utility Will Terminate With Condition Code 16 if it is Unable to Startup.<\/strong><br \/>\nPreviously if there was an environmental or administrative issue that prevented the utility to fully initialize it would end with a zero condition code which indicated incorrectly that the utility ran successfully.<br \/>\n<br \/>\n<strong>16. New Message JRBE508 Provides the FTP Filename that was Delivered.<\/strong><br \/>\nJRBE508 ** FILENAME:TSTDAT18_JOB18283_STD_gary.txt **<br \/>\n<strong><br \/>\n17. New Keyword to Specify Which TCPIP Region Should be Used: TCPIP_JOBNAME<\/strong><br \/>\nThis keyword supports situations where multiple TCPIP regions are being run in the same Z\/os image.<br \/>\n<br \/>\n<strong>18. Protection Against Intrusion by \"Web Crawlers\" added to the Web Server.<\/strong><br \/>\nThis is primarily in the form of the existence of a 'robots.txt' file.\/<br \/>\n<strong><br \/>\n19. AFP transformation Change using MPT.\u00a0 Now supports Mixture of Formdef\/Pagedef.<\/strong><br \/>\nPreviously it was assumed that ALL the DDnames that make up a JES output group used the same Formdef\/Pagedef.\u00a0 JRB can now accommodate each DDname that may have different Formdef\/Pagedef(s).<br \/>\n<br \/>\n<strong>20. New Keyword DELIVERY_FAILURE_NOTIFY_ID_DEFAULT<\/strong><br \/>\n<br \/>\n<strong>21. New Message Indicating Archive HFS is Full.<\/strong><br \/>\nIf an archive delivery fails due to the HFS being full there is now a delivery return code that specifically describes this:<br \/>\n\u00a0JRBE089 ** DELIVERY FAILED,RC=98 HFS MOUNTPOINT OUT OF SPACE<br \/>\nThis message will be issued to the console highlighted and will not roll off without manual deletion.<br \/>\n\"output descriptor=DESC=(2,7)\"<br \/>\n<br \/>\n<strong>22. JES_REPORT_SELECT_QUEUE_DEFAULT\u00a0 is now a Required Keyword<\/strong><br \/>\nSee section 14.2.286 JES_REPORT_SELECT_QUEUE_DEFAULT<br \/>\n<strong><br \/>\n23. Maximum Length of FTP Paths increased to 256.<\/strong><br \/>\n<br \/>\n<strong>24. Provide Ability to Choose Whether Imbedded Spaces are to be Removed from FTP Pathnames.<\/strong><br \/>\nNew Keywords:<br \/>\nFTP_COMPRESS_DIRECTORY_PATH<br \/>\nFTP_COMPRESS_DIRECTORY_PATH_DEFAULT<br \/>\n<br \/>\nThese new keywords are effective on the FTP pathnames specified in the following keywords:<br \/>\n\u00a0FTP_CREATE_DIRECTORY<br \/>\n\u00a0FTP_CREATE_DIRECTORY_DEFAULT<br \/>\n\u00a0FTP_WORKING_DIRECTORY<br \/>\n\u00a0FTP_WORKING_DIRECTORY_DEFAULT<br \/>\n\u00a0SEGMENT_OVERRIDE_FTP_CREATE_DIRECTORY<br \/>\n\u00a0\u00a0\u00a0<br \/>\n<strong>25. WEBPAGE_SIGNON_POPUP_BG_COLOR\u00a0\u00a0 is now an optional keyword.<\/strong><br \/>\nIt is only required when WEBPAGE_SIGNON_POPUP_MSG is also coded.<br \/>\n<br \/>\n<strong>26. Web \"Restore Document From History\" Change.\u00a0 Can now determine back media information from system catalog instead of JRB.<\/strong><br \/>\nNew keyword: WEBPAGE_HISTORY_RESTORE_CATALOG<br \/>\n\u00a0<\/p>\n","released_on":"2012-05-22T21:21:25.000000Z","deleted_at":null,"children":[{"id":597,"parent_id":494,"product_id":16,"release":"3.3.109","notes":"\n<p>\u00a0Maintenance release.<\/p>\n","released_on":"2014-11-17T23:21:25.000000Z","deleted_at":null},{"id":594,"parent_id":494,"product_id":16,"release":"3.3.107","notes":"\n<p>\u00a0Maintenance release.<\/p>\n","released_on":"2014-11-05T23:21:25.000000Z","deleted_at":null},{"id":573,"parent_id":494,"product_id":16,"release":"3.3.098","notes":"\n<p>\u00a0Maintenance release.<\/p>\n","released_on":"2014-07-15T21:21:25.000000Z","deleted_at":null},{"id":563,"parent_id":494,"product_id":16,"release":"3.3.089","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2014-03-11T21:21:25.000000Z","deleted_at":null},{"id":557,"parent_id":494,"product_id":16,"release":"3.3.083","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2014-02-06T23:21:25.000000Z","deleted_at":null},{"id":554,"parent_id":494,"product_id":16,"release":"3.3.076","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-11-05T23:21:25.000000Z","deleted_at":null},{"id":550,"parent_id":494,"product_id":16,"release":"3.3.074","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-09-10T21:21:25.000000Z","deleted_at":null},{"id":545,"parent_id":494,"product_id":16,"release":"3.3.060","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-06-28T21:21:25.000000Z","deleted_at":null},{"id":538,"parent_id":494,"product_id":16,"release":"3.3.055","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-04-24T21:21:25.000000Z","deleted_at":null},{"id":525,"parent_id":494,"product_id":16,"release":"3.3.043","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-02-19T23:21:25.000000Z","deleted_at":null},{"id":524,"parent_id":494,"product_id":16,"release":"3.3.040","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-01-31T23:21:25.000000Z","deleted_at":null},{"id":523,"parent_id":494,"product_id":16,"release":"3.3.037","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2013-01-17T23:21:25.000000Z","deleted_at":null},{"id":515,"parent_id":494,"product_id":16,"release":"3.3.023","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-10-29T21:21:25.000000Z","deleted_at":null},{"id":512,"parent_id":494,"product_id":16,"release":"3.3.017","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-09-26T21:21:25.000000Z","deleted_at":null},{"id":503,"parent_id":494,"product_id":16,"release":"3.3.015","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-07-30T21:21:25.000000Z","deleted_at":null},{"id":498,"parent_id":494,"product_id":16,"release":"3.3.007","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-06-05T21:21:25.000000Z","deleted_at":null},{"id":497,"parent_id":494,"product_id":16,"release":"3.3.005","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2012-06-04T21:21:25.000000Z","deleted_at":null}]},{"id":627,"parent_id":null,"product_id":16,"release":"3.4","notes":"<div>Applied JRB 3.2.01 - JRB 3.2.111 Some of these\nmaintenance items added significant functionality.\u00a0<\/div>\n<ol>\n<li>All maintenance from JRB 3.3<\/li>\n<li>TLS Encryption Security Support Added.\u00a0In addition to SSL, JRB\nnow supports TLS (Transport Layer Security) for both FTP and the JRB\ninternal web server. See section SSL_VERSION<\/li>\n<li>Removed All Virtual Storage Control Keywords.\u00a0All virtual\nstorage control keywords ($INIT) are now obsolete.<br>\nFor example: 2K_BUFFERS<br>\n2K_BUFFERS_EXPANSION_INCREMENT<br>\n2K_BUFFERS_STORAGE_LIMIT_TOTAL<br>\n...<\/li>\n<li>Keyword REPORT_NODE_SCAN is Obsolete.<\/li>\n<li>New Required $INIT Keyword START<br>\nSpecifies the JRB 'startup\nmode': HOT, WARM, COLD.<br>\nSee section START<\/li>\n<li>All Messages Generated by C++ Modules Now Being Sent to JRBLOG<br>\nPreviously these messages would appear on SYSPRINT. This change\nintegrates all pertinent messages into JRBLOG.<\/li>\n<li>Support For the Opera Web Browser Added<\/li>\n<\/ol>\n<p>\u00a0<\/p>\n","released_on":"2015-03-02T23:21:25.000000Z","deleted_at":null,"children":[{"id":724,"parent_id":627,"product_id":16,"release":"3.4.080","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2017-01-17T23:21:25.000000Z","deleted_at":null},{"id":722,"parent_id":627,"product_id":16,"release":"3.4.078","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2017-01-05T23:21:25.000000Z","deleted_at":null},{"id":705,"parent_id":627,"product_id":16,"release":"3.4.067","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-09-01T21:21:25.000000Z","deleted_at":null},{"id":701,"parent_id":627,"product_id":16,"release":"3.4.060","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-08-01T21:21:25.000000Z","deleted_at":null},{"id":695,"parent_id":627,"product_id":16,"release":"3.4.051","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-06-16T21:21:25.000000Z","deleted_at":null},{"id":688,"parent_id":627,"product_id":16,"release":"3.4.047","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-04-18T21:21:25.000000Z","deleted_at":null},{"id":681,"parent_id":627,"product_id":16,"release":"3.4.039","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2016-03-11T23:21:25.000000Z","deleted_at":null},{"id":675,"parent_id":627,"product_id":16,"release":"3.4.029","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2015-12-17T23:21:25.000000Z","deleted_at":null},{"id":649,"parent_id":627,"product_id":16,"release":"3.4.019","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2015-08-06T21:21:25.000000Z","deleted_at":null},{"id":626,"parent_id":627,"product_id":16,"release":"3.4.011","notes":"\n<p>Maintenance release.<\/p>\n","released_on":"2015-04-02T21:21:25.000000Z","deleted_at":null},{"id":625,"parent_id":627,"product_id":16,"release":"3.4.008","notes":"\n<p><strong>1.\u00a0Applied all maintenance from JRB 3.3 \u00a0\u00a0<\/strong><\/p>\n<div>\n <strong>2.\u00a0Added TLS encryption security support\u00a0<\/strong>\n<\/div>\n<div>\n In addition to SSL, JRB now supports TLS (Transport Layer Security) \u00a0for both FTP and the JRB internal web server. \u00a0\n<\/div>\n<div>\n See section SSL_VERSION\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>3.\u00a0Removed all virtual storage control keywords<\/strong>\n<\/div>\n<div>\n All virtual storage control keywords ($INIT) are now obsolete.\n<\/div>\n<div>\n \u00a0 \u00a0 \u00a0For example: \u00a0\n<\/div>\n<div>\n \u00a0 \u00a0 \u00a02K_BUFFERS\n<\/div>\n<div>\n \u00a0 \u00a0 \u00a02K_BUFFERS_EXPANSION_INCREMENT\n<\/div>\n<div>\n \u00a0 \u00a0 \u00a02K_BUFFERS_STORAGE_LIMIT_TOTAL\u00a0\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>4.\u00a0Keyword REPORT_NODE_SCAN is obsolete.<\/strong>\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>5.\u00a0Added required $INIT keyword START<\/strong>\n<\/div>\n<div>\n Specifies the JRB 'startup mode': \u00a0HOT, WARM, COLD.\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>6.\u00a0Sends all messages generated by C++ modules to JRBLOG<\/strong>\n<\/div>\n<div>\n Removes them from SYSPRINT\n<\/div>\n<div>\n \u00a0\n<\/div>\n<div>\n <strong>7.\u00a0Added support for the Opera web browser\u00a0<\/strong>\n<\/div>\n","released_on":"2015-03-26T21:21:25.000000Z","deleted_at":null}]},{"id":735,"parent_id":null,"product_id":16,"release":"3.5","notes":"<ul>\r\n <li>Removed auth code 1 AC(1) from all but the initial JRB load modules.<\/li>\r\n <li>Applied all maintenance from JRB 3.4. &nbsp;&nbsp;<\/li>\r\n <li>When the web server is configured to use SSL (SECURE_WEB_PORT) JRB no longer uses any unsecured port.<\/li>\r\n<\/ul>","released_on":"2017-06-08T14:43:51.000000Z","deleted_at":null,"children":[{"id":879,"parent_id":735,"product_id":16,"release":"3.5.122","notes":"<p>Maintenance Release.<\/p>","released_on":"2021-08-30T16:34:12.000000Z","deleted_at":null},{"id":873,"parent_id":735,"product_id":16,"release":"3.5.109","notes":"<p>Maintenance release.<\/p>","released_on":"2021-03-19T16:33:57.000000Z","deleted_at":null},{"id":861,"parent_id":735,"product_id":16,"release":"3.5.86","notes":"<p>Maintenance Release<\/p>","released_on":"2020-08-24T16:34:04.000000Z","deleted_at":null},{"id":848,"parent_id":735,"product_id":16,"release":"3.5.071","notes":"<p>Maintenance release.<\/p>","released_on":"2020-01-22T17:33:50.000000Z","deleted_at":null},{"id":828,"parent_id":735,"product_id":16,"release":"3.5.051","notes":"<p>Maintenance release.<\/p>","released_on":"2019-05-08T16:33:41.000000Z","deleted_at":null},{"id":827,"parent_id":735,"product_id":16,"release":"3.5.048","notes":"<p>Maintenance release.<\/p>","released_on":"2019-04-11T16:33:16.000000Z","deleted_at":null},{"id":813,"parent_id":735,"product_id":16,"release":"3.5.044","notes":"<p>Maintenance release.<\/p>","released_on":"2019-02-27T17:33:31.000000Z","deleted_at":null},{"id":807,"parent_id":735,"product_id":16,"release":"3.5.040","notes":"<p>Maintenance release.<\/p>","released_on":"2018-12-14T17:32:26.000000Z","deleted_at":null},{"id":789,"parent_id":735,"product_id":16,"release":"3.5.033","notes":"<p>Maintenance release.<\/p>","released_on":"2018-09-24T16:32:18.000000Z","deleted_at":null},{"id":781,"parent_id":735,"product_id":16,"release":"3.5.021","notes":"<p>Maintenance release.<\/p>","released_on":"2018-06-11T16:32:47.000000Z","deleted_at":null},{"id":779,"parent_id":735,"product_id":16,"release":"3.5.020","notes":"<p>Maintenance release.<\/p>","released_on":"2018-05-14T16:31:59.000000Z","deleted_at":null},{"id":778,"parent_id":735,"product_id":16,"release":"3.5.019","notes":"<p>Maintenance release.<\/p>","released_on":"2018-05-10T16:31:44.000000Z","deleted_at":null},{"id":749,"parent_id":735,"product_id":16,"release":"3.5.008","notes":"<p>Maintenance release.<\/p>","released_on":"2017-09-20T23:13:40.000000Z","deleted_at":null},{"id":748,"parent_id":735,"product_id":16,"release":"3.5.005","notes":"<p>Maintenance release.&nbsp;<\/p>","released_on":"2017-07-20T23:14:01.000000Z","deleted_at":null}]},{"id":882,"parent_id":null,"product_id":16,"release":"4.0","notes":"<p>Maintenance release.<\/p>","released_on":"2021-09-02T14:39:58.000000Z","deleted_at":null,"children":[{"id":931,"parent_id":882,"product_id":16,"release":"4.0.064","notes":"<p>Maintenance release<\/p>","released_on":"2023-02-15T17:35:59.000000Z","deleted_at":null},{"id":924,"parent_id":882,"product_id":16,"release":"4.0.062","notes":"<p>Maintenance release<\/p>","released_on":"2023-01-26T17:35:54.000000Z","deleted_at":null},{"id":917,"parent_id":882,"product_id":16,"release":"4.0.053","notes":"<p>Maintenance release<\/p>","released_on":"2022-12-02T17:35:49.000000Z","deleted_at":null},{"id":910,"parent_id":882,"product_id":16,"release":"4.0.051","notes":"<p>Maintenance release<\/p>","released_on":"2022-09-15T16:35:43.000000Z","deleted_at":null},{"id":899,"parent_id":882,"product_id":16,"release":"4.0.034","notes":"<p>Maintenance release<\/p>","released_on":"2022-05-03T16:35:38.000000Z","deleted_at":null},{"id":893,"parent_id":882,"product_id":16,"release":"4.0.031","notes":"<p>Maintenance release.<\/p>","released_on":"2022-03-23T16:35:30.000000Z","deleted_at":null},{"id":887,"parent_id":882,"product_id":16,"release":"4.0.024","notes":"<p>Maintenance release.<\/p>","released_on":"2022-02-08T17:35:24.000000Z","deleted_at":null},{"id":885,"parent_id":882,"product_id":16,"release":"4.0.018","notes":"<p>Maintenance release<\/p>","released_on":"2021-12-06T17:35:15.000000Z","deleted_at":null},{"id":881,"parent_id":882,"product_id":16,"release":"4.0.014","notes":"<ul><li><span style=\"color: rgb(0, 0, 0);\">All maintenance from JRB 3.5<\/span>&nbsp;<strong>&nbsp; <\/strong>\r\n  <\/li><li>Support for ZFS<\/li><li><a href=\"http:\/\/www.mackinney.com\/\"><span style=\"color: rgb(0, 0, 0);\">JRB 4.0 introduces database support via DB2<\/span>\r\n  <\/a><\/li><li><a href=\"http:\/\/www.mackinney.com\/\"><span style=\"color: rgb(0, 0, 0);\">Database support provides a technical basis for future, significant functionality additions<\/span><\/a><\/li><\/ul>\r\n<p><a href=\"http:\/\/www.mackinney.com\/\"><br><\/a><\/p>\r\n<p><\/p>","released_on":"2021-09-02T16:35:07.000000Z","deleted_at":null}]},{"id":947,"parent_id":null,"product_id":16,"release":"4.1","notes":"<p>Adds s<a href=\"file:\/\/\/K:\/MBC22.docx#_Startup_Commands\">upport for new MacKinney License Keys<\/a><\/p>\r\n<p><a href=\"file:\/\/\/K:\/MBC22.docx#_Startup_Commands\"><br><\/a><\/p>","released_on":"2023-09-05T21:05:21.000000Z","deleted_at":null,"children":[{"id":1037,"parent_id":947,"product_id":16,"release":"4.1.51","notes":"<p>Maintenance release<\/p>","released_on":"2026-01-29T18:08:32.000000Z","deleted_at":null},{"id":1033,"parent_id":947,"product_id":16,"release":"4.1.44","notes":"<p>Maintenance release<\/p>","released_on":"2025-11-13T21:27:34.000000Z","deleted_at":null},{"id":1003,"parent_id":947,"product_id":16,"release":"4.1.34","notes":"<p>Maintenance release<\/p>","released_on":"2025-04-22T19:03:04.000000Z","deleted_at":null},{"id":981,"parent_id":947,"product_id":16,"release":"4.1.023","notes":"<p>Maintenance release<\/p>","released_on":"2024-10-09T21:02:44.000000Z","deleted_at":null},{"id":969,"parent_id":947,"product_id":16,"release":"4.1.019","notes":"<p>Maintenance release<\/p>","released_on":"2024-07-23T16:38:35.000000Z","deleted_at":null},{"id":967,"parent_id":947,"product_id":16,"release":"4.1.015","notes":"<p>Maintenance Release<\/p>","released_on":"2024-04-18T21:38:36.000000Z","deleted_at":null},{"id":958,"parent_id":947,"product_id":16,"release":"4.1.006","notes":"<p>Maintenance release<\/p>","released_on":"2023-12-18T16:59:29.000000Z","deleted_at":null}]}]}