Issues resolved in v17.6.26:
- Ticket#2878 - COND specification on PROC steps properly merged with those on JOB steps
Issues resolved in v17.5.19:
- Ticket#2848 - JOB card positional parameters are optional
- Ticket#2849 - System utilities ignore line sequence numbers for input cards
Issues resolved in v17.4.23:
- Ticket#2830 - quoted keyword parameter values allowed
Issues resolved in v17.2.14:
- Config - Changes to configuration applied immediately
Issues resolved in v16.11.17:
- IDCAMS - Improved VDB (VSAM Transparency Mode for record-at-a-time file access), including COBOL-compatible "split key" support in the DEFINE statement
- Nested IFs - Fix for deeply nested JCL IF statements
Issues resolved in v16.8.17:
- EBP-Plex - Deadlock removed during checkpoint / restart activity in a multi-node EBP clustered environment
- LOCK Web Service - LIST operation will display all locks held by a node or across an EBP-Plex
Issues resolved in v16.8.4:
- Ticket#2680 - PROC card can have comments in columns 72-80
- Elastic IMS DB - EBP IMS DB compatible with ETP operations as well
Features introduced with v16.7.27:
- EBP-Plex - Job name locking issue resolved
- JCL - BUFNO=(n) support
Features introduced with v16.7.17:
- Elastic IMS DB - Introduction of Elastic IMS DB support. Note: Requires upgrade of Elastic COBOL to v16.7.17 or higher.
Issues resolved in v16.6.23:
- Ticket#2636 - COBOL applications with prefixes on ASSIGN TO clauses (e.g. UT-S-MYDD) are mapped to correct DD name within EBP (e.g., MYDD)
- Ticket#2631 - Testing RC within PROCs; Job-level COND testing of PROC steps as a whole
- Ticket#2622 - SyncSort control cards now allowed in in-line and cataloged PROCs
- Ticket#2623 - RESTART at specific step name
Features added in v16.6.8:
- IDE - Eclipse Elastic COBOL plug-in support to display and submit JCL to EBP
- SPACE - Adjusted SPACE calculation by UNIT, see Tape Handling and Unit Specification
Features added in v16.4.28:
- RAC - Ability to build custom resource access control modules via the IRAC Interface
Features added in v16.3.29:
- US811 - IBM JES2 v2r2 (August, 2015) compatible job class names supported (not just letters and digits) for JCL CLASS parameters and EBP Web Services.
Features added in v16.3.17:
- US811 - Job Execution Control as defined in IBM JES/JCL V2R2 (released August, 2015) allowing scheduling of jobs with the following JCL cards:
- // SCHEDULE WITH=another-job
- // SCHEDULE HOLDUNTL=+hh:mm | (hh:mm,mm/dd/yyyy) | (hh:mm,ddd/yyyy)
- // SCHEDULE STARTBY=+hh:mm | (hh:mm,mm/dd/yyyy) | (hh:mm,ddd/yyyy)
- // SCHEDULE JOBGROUP=jobgroup
where JOBGROUPs are defined by submitting a job of type JEC associating many jobs. A job class of type JEC previously defined and an initiator of that class started. Example (from IBM JES/JCL Reference V2R2):,
//* DEPENDENCY NETWORK:
// CONCURRENT NAME=JOBA
// BEFORE NAME=JOBA
// AFTER NAME=JOBA
Issues resolved in v16.2.15:
- Ticket#2541 - Allow EBP to work with older JVMs; IDCAMS DEF IDX for Windows
Features added in v16.1.23:
- DSNTYPE - JCL DD statement parameter allowing specification of PIPE, allowing piping of datasets from one job to another.
- VDB File Format - VDB file protocol (VSAM transparency mode, records as BLOBs in database tables) supported, PROTOCOL=VDB for DD DCB and IDCAMS. MySQL, PostgreSQL, DB2, Oracle supported for KSDS, RRDS and ESDS compatibility. IDCAMS REPRO REUSE / REPLACE keywords verified on all file formats.
Features added in v15.11.20:
- VSE JCS Jobs - Support added for IBM VSE JCS mode JCL: define JCS-type job classes, explicit submit of JCS or JCL dialect.
- SCRIPT Jobs - Support added for arbitrary scripting for sh, bash, csh, ksh, rexx: define SCRIPT-type job classes, explicit submit of SCRIPT or PYTHON dialect, shellcommand configuration.
Features added in v15.11.5:
- Ticket#2512 - Correct syntax error when multiple symbolics are used in keyword parameters.
- DD SYSOUT - other parameters (e.g., DCB) are allowed with the SYSOUT parameter
- RAC - correction to cached authenticated users
Features added in v15.10.28:
- Ticket#2509 - Use DD keyword DCB=PROTOCOL=VSQL to indicate VSAM-to-SQL bridge references to files, DSN=a.b.c.d.e must match the property VSQL.a.b.c.d.e contained within the data.properties file within the STEPLIB or JOBLIB or systempath1..9 jars from which the program is executed. Similarly, deploy_settings file contains database connection information and references to the XML column mapping file also contained in the jar for each VSAM file that is mapped. See https://heirloomcomputing.zendesk.com/entries/23396577-Using-the-VSAM-SQL-Data-Bridge for more information.
Features added in v15.9.17:
- INCLUDE - support for the INCLUDE card in JCL whose MEMBER keyword indicates a member (i.e., file) within a PDS (i.e., directory) that is to be included in the current step (e.g., DD cards) or add additional steps (EXEC cards and their DD cards) at that point in the job. Group INCLUDEs also supported
- Ticket#2488 - support for PROC-less PROCs, cataloged procedures that do not start with a PROC card. PROCs are pulled from the JCLLIB specified within the job or from the jcllib1..9 configured directories.
- Ticket#2493 - respect autocommit, isolation and implicit SQL properties in the IKJEFT.properties file for IKJEFTxx programs
- Ticket#2495 - when authorizing resources without authenticating users, allow searching LDAP for user's groups with rac.userbase and rac.usersearch
- Ticket#2485 - exception on concatenated DD cards
- Ticket#2486 - multi-line IF statements, added support for IF stepname.ABEND testing
Features released and problems resolved in v15.8.28:
- RAC - case insensitive checking of user ids and resource names
- Wildfly (JBOSS) form of JAAS credentials supported in RAC
- Resource Groups introduced in Resource Access Control. Resource groups may be defined in the LDAP directory that contain both resources and groups that have access to them, creating a M:N relationship between the two.
- Ticket#2476 (RAC) UNIT keyword of DD statement accepts a UNIT=(unit-name) and UNIT=(unit-name,unit-count) in addition to UNIT=unit-name and UNIT=AFF=unit-affinity. The unit-count is ignored, but the unit-name can be used to designate a dataset mapping to configured datadir.0..9 paths that include the name in the path. See documentation for more info on dataset mapping.
Features added in v15.6.5:
- Resource Access Control (RAC) is introduced leveraging Java Authentication, Authorization Service (JAAS), Java Naming Directory Interface (JNDI) and Lightwight Directory Access Protocol (LDAP) together with J2EE Application Servers (Websphere, Weblogic, JBOSS, Geronimo) or J2EE Servlet Engine (Tomcat, Jetty) to provide mainframe compatible authentication and authorization. See the Integrated Security section in the Elastic Batch Platform overview article and the RAC: Operating EBP and ETP in a Secure Environment detailed article.
Features added in v15.5.22:
- ER: Integrated Security is introduced
- ER: BPXBATCH standard utility for invoking a shell script is introduced
Problems resolved in v15.4.30:
- Ticket#2424:Verified IDCAMS DEFINE CLUSTER record and keylength settings can be read by COBOL applications with the same attributes
- Ticket#2426: Resolve IDCAMS REPRO blocking/deblocking issue which cause input/output records and bytes to differ
- Ticket#2421: Output queue elements restored after server stop/start
- Ticket#2426: VSAM-to-VSAM REPRO record count corrected
- Ticket#2420: Record blocking with DCB overrides on DD card
- Ticket: System Operators Console updates for HTML5.
- ER: Allow initiator changes while system is quiesced
- ER: Define output spooler classes A-Z referenced in OUTPUT statements, MSGCLASS and SYSOUT parameters that (1) hold (default), (2) none (spooled output is thrown away), (3) lpr (sent to Linux defined line printer, (4) log (sent to defined Java log4j logs), or (5) arbitrary spooler programs (e.g., LRS)
- ER: Change EBP configuration properties from jes.xxx to ebp.xxx; deployment package from jes.war to ebp.war; deployment context from /jes to /ebp
- ER:Provide EBP XML Schema for all REST Web services
EBP is included in every subscription of the Heirloom PaaS and is available when you start your cloud instances. Sign up at paas.heirloomcomputing.com to run the JES/JCL engine in the Heirloom PaaS cloud. Or, contact us to run EBP on-site with your Elastic COBOL subscription. Use your existing license file or deploy the new one you receive at one of the following locations.
- The home directory of the user running the Servlet container or Java Application Server (e.g., /usr/share/tomcat8/elasticcobol.properties, C:\elasticcobol.properties)
- The directory containing the EBP Web application (e.g., webapps/ebp/elasticcobol.properties)
- In the ebp.war itself before being deployed to the Web server (with the command "jar uf ebp.war elasticcobol.properties")
Your EBP server must have access to paas.heirloomcomputing.com to verify the license file when it starts up. Or, follow the "Proxy License Validation" procedures described under "Licensing as a Service" on this forum.
EBP also runs on private clouds and local Windows, Linux, and UNIX servers.
Download EBP from the following link
to the Tomcat 7 or 8's webapps folder. Or, deploy using Tomcat admin site http://localhost:8080/manager
- Access your EBP system using http://localhost:8080/ebp
- Rename to ebp.war (Tomcat version numbering scheme doesn't work under Geronimo) and copy to the server's deploy folder or deploy using the server's Web deployment mechanism
- Access your EBP system using http://localhost:8080/ebp
- For the IBM Websphere Liberty Profile Server, use the command "jar xf " to extract the contents of the EBP distribution into a directory named usr/servers/defaultServer/dropins/ebp.war (i.e., ebp.war is a directory) in the Websphere Liberty Profile installation directory as it will not automatically unpack wars into working directories.
- For the Red Hat JBOSS Application Server and Wildfly, use the command "jar xf " to extract the contents of the EBP distribution into a directory named $JBOSS_HOME/standalon/deployments/ebp.war (i.e., ebp.war is a directory). Then create a .ebp.war.dodeploy file in the $JBOSS_HOME/standalon/deployments directory.
- Access your EBP system using http://localhost:8080/ebp (JBOSS, Weblogic) or http://localhost:9080/ebp (Websphere Liberty)
- Use the command "jar xf " to extract the contents of the EBP distribution into a directory named ebp, such as /usr/local/ebp.
- Add this runtime variable to the Weblogic startup script. -DUseSunHttpHandler=true
- Access the system with http://localhost:7001/ebp
Operate EBP without a servlet engine or Java Application Server.
- Start EBP with the command
- You can set various parameters such as the HTTP listen port. Use --help option for more information
- Access your EBP system using http://localhost:8080/ . To access it as http://localhost:8080/ebp use the --context /ebp command line option
- http://heirloom.cc > Menu > Support > Forums > Elastic Batch Platform or direct link
Overnight (latest) builds of EBP are available at