MacKinney Systems, Inc.

Released On: 02/07/2007

  1. All maintenance available for 2.2 has been applied to 2.3.
    JRB 2.2.01 - JRB 2.2.46 have been applied.
  2. You now have control of the number of route entries delivering simultaneously. New keywords for $INIT:
      default TCLASS for deliveries.  (required keyword)
      concurrent deliveries for this class.  (required)
      concurrent deliveries for this class.  (required)
      concurrent deliveries for this class.  (required)
      concurrent deliveries for this class.  (required)
      concurrent deliveries for this class.  (required)
  3. New keywords for route entries:
    DELIVERY_TCLASS - sets TCLASS for a specific route entry.
  4. The above keywords implements a maximum active number of tasks in each of five classes.  To implement:
    • Decide how many route entries you want to allow for each TCLASS.
    • Specify the TCLASS for each route entry.
      You can use a combination of.
      TCLASS has no effect on priority.... There are other keywords for that.  It simply controls the maximum number of concurrently delivering route entries in a given TCLASS.
    • Drastic reduction in resource usage.

  5. Changes have been made to the internal task dispatcher.  Previous versions maintained an internal JRB task for each route entry started.  This version will require an internal JRB task ONLY when a particular route entry is actually delivering.  This will result in a drastic reduction in the numbers of internal tasks, and their buffers, required for a given throughput.  The bottom line will be a much leaner JRB.  The real storage needed for a given amount of throughput will drop dramatically. This will show up in the following:
    • Smaller real storage demands for JRB
    • Smaller value for MAX_NUMBER_INTERNAL_TASKS
    • Smaller value for 2K_BUFFERS
    • Smaller numbers of transmit buffers allocated.
    • Smaller number of JES read buffers
  6. These changes will show up on your z/OS monitor (or SDSF) and the values reported by the SHOW command.  Also it will show up in the tasks reported by the DISPLAYTASK command (compared to previous versions).


The following changes were implemented by maintenance items in JRB 2.3 and carried forward to JRB 2.4

MAINT 2.3.26

  1. Provides the ability to specify a codepage to be used when converting a document from EBCDIC to
    New (required) keyword:
  2. Provides a new, optional, customizable message issued at delivery time.
    New keyword:

MAINT 2.3.26

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.

New keywords:

The keyword REPORT_SEPARATOR_USERID can now include any of the supported substitution variables.

MAINT 2.3.24
Provides the ability to specify a 'control' record that is imbedded in the report to be delivered. These control
records can specify delivery parameters and influence the way the report is delivered and split up.
New keywords:

MAINT 2.3.21
Adds a new FUNCTION called FIND_STRANDED_GROUPS to the JRBMUTIL batch utility program.

MAINT 2.3.20
Added support for mixed-case passwords on the web signon page with a new required keyword,

MAINT 2.3.19
Added the capability to select reports from the Held queue via the following new keywords:

When these keyword(s) are not present then reports will be selected from the Output queue, which is the
default when neither HELD nor OUTPUT is specified.

MAINT 2.3.18
Added a new possible value to following keywords:



This provides the ability to customize the report group tree web page to display the name of the group first, followed
by the description... separated by a dash ('-').

MAINT 2.3.13
Provides support for new substitution variable &SP. A single space will be substituted in its place. The
substitution will take place AFTER the normal blank compression. It can be used to place a space in keywords
whose values have all spaces normally compressed such as:

MAINT 2.3.10

Added support for the ROOM parameter from the OUTPUT JCL statement.

  1. WEBPAGE_REPORTDIR_COLUMN_NAME now accepts the value OUTPUT_ROOM. It adds a column to the report directory web page.
  2. 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.
  3. Support for the ROOM parameter was extended into the 'Send Report to JES' function from the report directory web page.
  4. New required keyword in the $WEB member. WEBPAGE_REPORTDIR_OUTPUT_ROOM_LEN

MAINT 2.3.06

  1. Added ability to specify a variable in these keywords:
  2. 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.
  3. 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).
  4. New message JRBE409 that indicates the completion of a delivery.

MAINT 2.3.02
Added new substitution variable &ACCT(n).
Accounting Information fields from JOB card. n is the relative position of the parameter desired.
For an example of its use see FTP_FILENAME