Control Products
OAK develops and supports various tailor made solutions for BMC Software’s products. All the solutions are installed and working at various BMCs' customers. Solutions may be tailored to any specific requirements.
In order to learn more, click on the product title.
For more information please use the Contact Us page.
|
CONTROL-D Printing of Record Level Index The OAK Printing of Record Level Index solution allows the print of a single index value, retaining the heading, but eliminating all lines not belonging to the requested index value. This solution is very important when the printed paper need to be given to a client and privacy is important. This feature supports dynamic headings (based on PDS member definitions), dynamic page line count and also supports multiple occurrences of the same value while re-constructing the page layout. The solution keeps in memory the heading lines, builds a memory image of the page, while accepting the valid lines only (based on RBA ranges). It handles the page size and automatically re-inserts the heading. Use our Contact Us page for more information |
Go up|
CONTROL-D Shrink Wrap Support The OAK Shrink Wrap support enables to limit the number of pages that will be created in a CONTROL-D print mission bundle to the number of pages required by the shrink wrap machine. During the printing process, each time the specified number of pages is reached, the active user bundle is automatically closed as a segment and a User End Banner is produced. Additional segments are produced starting with User Start and ending with User End banners until the entire bundle is printed. Optionally, each segment can be numbered in the order that they are produced and printed. Using the OAK Shrink Wrap support, shrink wrap or similar machines can be productively used with CONTROL-D bundle printing. Use our Contact Us page for more information |
|
CONTROL-D and OPC/ESA/Tivoli Interface The OPC/ESA
to Control-D Interface enables OPC/ESA to examine a previous job
run output in order to perform a successful rerun. Use our Contact Us page for more information |
|
CONTROL-D Report Delivery Date Handling The OAK Report Delivery Date Handling feature enables
to determine when reports are to be printed, regardless of when
they were created. Each report can be defined its own delivery date. The OAK Delivery Date Handling feature enables to ensure that reports will be printed according to precise business needs and service level agreements by report type rather then FIFO (first in first out). The OAK Report Delivery Date Handling feature also
provides an additional sorting criteria for the bundling of reports. Use our Contact Us page for more information |
|
CONTROL-D Enhanced SMF Accounting Support The OAK Enhanced SMF Accounting Support enables to write an additional 20 characters of unique information on a recipient level to the SMF records written during the print mission process. In organizations that have standards of identifying recipients for accounting and charge back by either: An identification different than the CONTROL-D Recipient Tree unique 8 character name ¨ An identification longer than 8 characters The OAK Enhanced SMF Accounting Support enables to write the required information to the SMF records. The additional 20 character field can also be used for other purposes than recipient identification. Information from the print mission definition can be written to the SMF records as well. This provides organizations with additional information for various accounting calculations or other uses. Use our Contact Us page for more information |
|
CONTROL-D Dynamic Recipient Identification by Ranges The OAK Dynamic Recipient Identification by Ranges feature enables to identify a recipient by specifying a numeric range as a synonym in the CONTROL-D Recipient Tree. Each recipient needed to be identified by a numeric range or multiple ranges will have one synonym defined for each range in the CONTROL-D Recipient Tree. In the example described above, recipient A would simply have ranges 1,000 to 2,000 specified in the recipient tree and the decollation process will automatically assign the correct report pages to recipient A. Some CONTROL-D users implement numeric range support by utilizing decollation mission WHEN statements. The main drawbacks of using the WHEN statement approach are poorer performance and on-going maintenance overhead. The poorer performance is a result of having to specify many more WHEN statements since the DO USER=* method cannot be used. When there are more WHEN statements, CONTROL D needs to analyze more identification instructions for each page processed. The on-going maintenance overhead is a result of having to maintain the numeric page ranges in each decollation mission separately. When using the OAK feature, the numeric page ranges are centrally maintained in one place for all reports, in the CONTROL-D Recipient Tree. If a recipient is assigned an additional range of pages, it only needs to be updated in one central place. In addition, maintaining decollation missions with many WHEN statements is naturally more overhead then maintaining decollation missions with less WHEN statements. Use our Contact Us page for more information |
|
CONTROL-D Generic Processing for CDAM Decollation The OAK Generic Processing for CDAM Decollation combines the superior benefits of the pre-spool output retrieval method with the extremely efficient generic processing. Similar to the report grouping considerations used when implementing generic decollation missions, reports that are produced directly to CDAM (pre-spool) are assigned a single decollation structure. A skeleton decollation mission is defined for each structure group. The correct skeleton is loaded according to the skeleton table. As the job executes and while the report is being written to CDAM, the skeleton fields are resolved. The resulting decollation ON block is dynamically added to the decollation mission definition on the target decollation mission library. This step is repeated for every CDAM file created (on a JCL DD card level) throughout the job. At the job’s termination, the dynamically created decollation mission is ready to process. Decollation missions dynamically created using the OAK Generic Processing for CDAM Decollation are built in the most efficient way possible. Each CDAM file has it’s own dedicated decollation mission ON block. This results in eliminating possible mistakes and provides optimum decollation performance. Use our Contact Us page for more information |
|
CONTROL-D Automatic Retrieval of CONTROL-M ODATE The OAK Automatic Retrieval of CONTROL-M ODATE feature enables generic decollation missions to automatically retrieve the CONTROL-M ODATE of the job being decollated. This enables one generic decollation mission to process multiple job outputs with different CONTROL-M ODATEs, while correctly retaining the ODATEs. All reports, including those processed by generic decollation missions are assigned the correct ODATE in full synchronization with CONTROL-M. This results in accurate output selection criteria by business working day. For example, ability to view a subset of the jobs belonging to yesterday’s working day. Use our Contact Us page for more information |
CONTROL-D Web Document / Image Viewing The Web Document / Image Viewing is designed to allow viewing of any document stored in Control-D archiving system. The product allows easy integration into existing web sites while relying on existing security and authentication systems. The product integrates into your existing website with emphasis on minimal end-user dialogs and mouse clicks. The software uses the API technology provided by the archiving software (Page On Demand API Toolkit for Control-D) to access the document archives. It uses Adobe™ ColdFusion as the web application deployment platform. Special development emphasis was given to software performance and resource consumption by the mainframe computer to ensure fast response time and short end-user wait time. End-user Authentication may be tailored to existing hosting web site. The authentication process translates the userid/password into Account Number(s) (which become the allowed Index value). An optional module, notify end-users by email when new documents are available for viewing. This optional module sends out emails with a direct URL the takes the user (after authentication) directly to view the new document. The product is not dependent on Control-D/Webaccess. It can be implemented in parallel. Use our Contact Us page for more information |
Enterprise Report Catalog An essential product for every Control-D/V user. ERC - Enterprise Report Catalog is a product that provides Control-D/V users with a comprehensive catalog of all the reports processed by Control-D. How many times a user asked if he could pick a report, either to browse or print, from an “album” like catalog? Now it is possible! ERC maintains a list of all reports found in Control-D Active User File. ERC keeps as much information on each report as can be found within Control-D. ERC takes sample pages from the report data and archives these pages for later catalog printing. The catalog can also be decollated by Control-D/V for Online-viewing. It is simple and easy, just run a job that looks at Control-D AUF and ERC either creates or updates its database with page samples for each report found. All information that can be gathered about the reports are recorded as well. In the case that Control-M is used, additional information is collected to display the production schedule of every report and more. To allow end users easy access to reports on the ERC, Control-V users can create an index by report-name and/or any other available META data, which will provide them with quick search and view on all report names. It grants the users faster search hence enabling easy viewing as well as easy printing. A User Exit is provided to allow sensitive data to be scrambled on the sample pages. Reports processed by other systems (non Control-D/V) can also be stored in the ERC. Use our Contact Us page for more information |
|
CONTROL-M Auto-Edit by Date (OAK-Date) Utility There are great advantages in using the CONTROL-M Auto-Edit facility, which are realized by most CONTROL-M users. After examining many Auto-Edit implementations, date dependent variables clearly lead in the type of Auto-Edit variables that are used. As the use of date dependent Auto-Edit variables get more complex, the lack of flexibility for handling dates in Auto-Edit starts to create a challenge to implement. Many type-of-day dependencies simply cannot be calculated. For example, the last working day of the previous quarter, or the first Monday of next month. These type-of-day calculations require the use of calendars, which is not available by Auto-Edit. This results in manual preparations, or in other words a lot of time and effort. Many applications may reference a date in different formats. For example, one application may reference a date by MMDDYY, while another application may reference a date by YYMMDD. Changing the Auto-Edit date format requires to use a large number of Auto-Edit functions. Auto-Edit global members are frequently built in order to simplify the usage of date dependent variables within JCLs. A big challenge that CONTROL-M Auto-Edit users have is to build the global members. The OAK CONTROL-M Auto-Edit by Date (OAK-Date) utility is a comprehensive and flexible tool that enables to automatically build date dependent Auto-Edit global members. The OAK Date utility enables simple and quick definition of any type-of-day and in any format. Auto-Edit implementations can now handle complex date dependent variables with no on-going manual efforts. The utility has a special simulation mode that enables to see the precise results of the OAK date variables. The simulation is very useful to test new variables without influencing the production environment. Use our Contact Us page for more information |
|
CONTROL-M Sysout Viewing from CONTROL-D When
using CONTROL-M Status screen to View a job’s Sysout, only the first
three files are accessible. When
working with both CONTROL-D and CONTROL-M, the job’s message class
is archived by CONTROL-D. This allows viewing of all message class
files, not just the first three files. However,
even while working in this shared environment, only the first three
files of a job’s Sysout can be accessed from CONTROL-M’s Status
screen. The
purpose of this enhancement is to improve user productivity by enabling
the user to access the information needed to complete a successful
rerun without leaving CONTROL-M Status Screen. This
feature dynamically checks if the job’s Sysout is already decollated
by CONTROL-D, in which case it enables the CONTROL-M’s viewing to
use the CONTROL-D CDAM instead of the standard CONTROL-M viewing. Using
this feature enables the same viewing on the EnterpriseControl Station
too. Note: The Sysout viewing in CONTROL-M is available only when CONTROL-R is installed. Use our Contact Us page for more information |