Recent Activity

SymDump for CICS: Protect Last Screen Image Last Screen Image access should be protected by external security so no unauthorized access is allowed. See Last Screen Image description on Working with Dumps DocOps page for more details. The general problem is to restrict unauthorized personnel accessing potentially sensitive data like…

CA is rapidly bringing innovation to the Mainframe Intelligent Operations and Automation market. Don't miss out on this solution demo so that you keep current through live demonstrations. The solution enables your team to expedite detection and resolution of performance problems through deep-dive analytics, automated alerts and powerful predictive…

Issue: 21769262 01 I would like to code PARMDD=*** in a processor to re-direct parm to a file - the chief advantage of this is that it bypasses the 100 byte maximum length that can be passed in a parm (see sample JCL below). Business Value: Eliminates the need for multiple IF-THEN-ELSE Reduces trouble-shoot and overall…

Incremental Release Delivery 11.0.03 PTFs have been published. Summary of Changes in Version 11.0.03 PL/I 5.2 Support Maintenance Please refer to the Release Information section of the product documentation for more information on these changes. The complete Version 11 product documentation is available at…(Show moreShow less)

I have been using Endevor package processing with shipment for many years and have shipped failed packages in the past as well. Recently I needed to ship a failed package, and when doing so the shipment failed. What I found out about the failure and the shipment process: It was due to a processor execution that failed on the Link-edit…

When using and developing Endevor processors the use of ISPF variables is accessed via a Clist or Rexx program. it would be a great help to many administrators if Endevor could access a developer's user ISPF profile and have access to their variables when writing processors and needing variable within the processor without the need for a Clist or…

Interesting idea, if this was portable. Meaning that the specific element(s) that went through a processor with (user A)'s ISPF profile variables is available for (user B) to use later. Why? Because (user A) went on vacation, won the lottery, reassigned to another development team and (user B) has to take over. Tying down an…

As an Endevor administrator, any utility to identify syntax failures will save time and efforts. The new option for Event Logging calls for new syntax written to the Endevor Parmlib member defined in the C1DEFLTS table. The only method for building the syntax for the E2ELOGMBR is through free form editing. Then, once the syntax is defined to…

As an Endevor Administrator with multiple Endevor systems in multiple configurations, Element Action event records can only be written to a single location on USS because the parser only supports syntax for a single TO PATH location. The syntax for the FROM ENV will allow masking, if the naming convention for the Endevor System is not unique,…

From the documentation I assumed this would be how it already worked, we are due to test this functionality later this week, hopefully one that can be squeezed into 18.0.12 seeing as it's already postponed?

When implementing Event Logging (E2ELOGMBR in C1DEFLTS), one defines a USS director to store the event records (for Element Actions and Package Actions). The record is written to the USS, but there is no reference to that record creation in the message log (C1MSGS1). To determine the USS location, one has to browse the PARMLIB library member…

As a customer, I need the ability to ship whatever I want whenever I want in order to support agile and waterfall development methodologies at my site and provide a proper and trustworthy "source of truth" in Endevor. Tying package shipment to packages that have executed “actionable/destructive” activity only (i.e. GENERATE, MOVE) is, with the…