Rocket Mainframe DevOps

Status: DeclinedDeclinedWe need to scratch several components of the same libtype.  We would like to use the XML SCRATCH COMPONENT SERVICE.  It seems to only allow one member at a time.

The rapidly expanding growth of distributed ZMF clients can be attributed to a more intuitive user experience,  smart editors, integrated debuggers and more.   As this technology becomes more widely implemented,  customers have requested  stronger network security for their ZMF Environment.  Specifically the request has come in for all ZMF communications to be encrypted using the strongest version of TLS.   The Secure Sockets Layer (SSL) protocol was designed by Netscape in 1995.  SSL went through many iterations and has now been effectively replaced by Transport Layer Security (TLS).   The terms SSL and TLS have become somewhat interchangeable, but they both exist to provide secure transport for your communications.  We have all used TLS Encryption technology when accessing sensitive data over the internet by using the https protocol .    Implementing TLS for ZMF distributed clients is fairly straightforward. 

Has anyone modified exit 9 (CMNEX009) to exclude adding approver by application? Currently an approver is added whenever libtype equals XYZ. Working as designed. We would like to have exit 9 as I mentioned above also to exclude adding XYZ if application equals ABDC. Any assistance would be greatly appreciated.#ChangeManZMF

As much as we may hate to admit it, problems do sometimes arise in the ZMF Server started task that may lead to an abend (and I hasten to stress that these are not always Serena's fault!).  Also, back in the dim and distant past that coincided with the release of ZMF 7.1, the recommended started task dump file contained in the SERVER sample CNTL member changed from the tried and trusted: //SYSUDUMP DD SYSOUT=* *Abend list to the new (and slightly mysterious for some): //SYSMDUMP DD DISP=(MOD,CATLG,CATLG), * SYSMDUMP // DSN=somnode.SERCOMC.SYSMDUMP( 1), // UNIT=SYSDA,SPACE=(CYL,(200,100),RLSE), // DCB=(DSORG=PS,RECFM=FBS,LRECL=4160,BLKSIZE=4160) Many of our customers are comfortable with SYSMDUMPs.  However, if you are unfamiliar with this format, have never made the change to your started tasks’ JCL, are wondering why this happened, how

I am trying to trace why a promote job is not building a refresh of a WLM environment for a DB2 stored procedure. Is there something that can be added to a job that shows you variable values that impact what is and isn't included in JCL? I've been blessed with administration authority with no formal training. Thanks!#ChangeManZMF

If you have not installed ZMF 8.1 yet and tried the high level exits out you need to soon. In addition to giving us the flexibility to use COBOL, REXX or any other high level language, the developer have made it easy to get variables and even easier to pass variables between stages or even between sessions. Today I just want to share how to use REXX to read a file for validating the Work Request ID. -- It sounds simple but until now unless you were able to program in assembler or only accessed ZMF through the ISPF interface it wasn't possible. The sample code is just that -- probably not that useful in a production environment -- but it depends. Remember that a REXX program can't read a VSAM file so you have copy it to a flat file or use another language. Also since there is no TSO environment in the high level exit you have to use BPX WDYN to allocate and free files - this is a standard utility on all mainframes. Here is the example of that call: RC = BPXWDYN("ALLOC DD("ddname") DA('

Status: DeliveredThis has been completed in ZMF 8.2 Patch 6. This will now check across applications the same as in checkin for overlay.  Currently, the release settings (share baselines, related applications) are used to determine the syslib concatenations.  These settings are not used by the test area function, which examines the release applications separately.  The Test Area function should examine across applications with shared baselines, and so should the Test Release Function. When you have 2 or more applications defined and attached to a release in ERO, and these applications share baselines, the TA (test area) command doesn't identify common components between the application packages.

This video gives a brief demonstration of the ZMF package component mass rebuild function.#ChangeManZMF#Videos#Announcement

This video gives a brief demonstration of how to activate and drive a High Level Language eXit (HLLX) within the ZMF Build function.#Videos#Announcement#ChangeManZMF#HowTo-BestPractice

Status: DeliveredMarking as Delivered.Would like to see a Panel Option to display ERO release approvals. Currently the only way to see them is via the log.

Status: DeclinedFor something as simple as setting a single panel variable to a default value putting a new set of HLL exits pre and post is overkill. Just hardcode the value in the panel logic. No updates for the clarification asked 6 years ago and no up votes mean this is being declined.ADD HLLX SERVICE FOR CMNSTG16 COMPARISON PANELWE OFTEN ARE ASKED TO SET A DEFAULT OPTION BY DEVELOPERS, ONE SUCH CASE IS THE CMNSTG16 COMPARISON SCREEN THAT USERS WANT THE COMPARSION REPORT DISPOSTION TO BE SET TO "3 - Delete dataset without printing" I KNOW SERENA DEFAULTS WHEN BLANK TO "3 - Delete dataset without printing"  BUT DEVELOPERS WANT IT CHANGED EVERY ENTRY. AT THIS POINT I DO NOT SEE A HLLX FOR CMNSTG16 AND SUPPORT HAS NOT FOUND ONE. SO FOR V811 CAN ALL STAGE PANEL USED HAVE A HLLX EXIT AVAILABLE FOR FIELDS USED (SPECIFICALLY IN THIS CASE CMNSTG16 IS NEEDED)        

We currently have one customer asking for an enhancement to incorporate Monitor / Limbo into HLLX. The enhancement was created, however in order to value the usability or value of this enhancement, we'd like to get some feedback from the customer base on what their thoughts are on this enhancement. Is it something that you will use in your shop, or will you continue to do what you do now for Monitor / Limbo issues? #Announcement#Other#ChangeManZMF

Question posted 7/7/08 by lromanDetails:We are thinking of using Unix System Services on our mainframe environment.Is anyone using z/OS Unix System Services and, if you are, is it in an integrated way with ChangeMan ZMF or are you bypassing ZMF altogether or perhaps using something like ChangeMan DS or Dimensions? #oldforumpost#unixsystemservices#ChangeManZMF#post085899b020

Discussion posted 3/28/08 by Serenity ThompsonDetails: dansladekIn our shop, we have a number of contractors who work for awhile and then leave. They also leave CMZMF packages which need to be reviewed, deleted or re-assigned to someone else. I understand XML services change the package creator id but we haven't really used XML services. Does anyone have any code which will do this for me? Thanks!Posted 9/26/2007 2:01 PM jokkespeedHi,We are usign a software from AbitMORE bvba (Commander). It has pre-built solutions that solve this problem. It also comes with a REXX generator, as you can see included in this note. If you would like to now more about the Commander (have a look at www.abitmore-scm.com). It has a neat userinterface to the XML Services. Even for complex update scenario's we don't write any rexx code, but use the standard interface of the tool.As stated here is the rexx code, if you have any problem it getting up and running chip me a mail :/* REXX *//*================

Discussion posted 3/28/08 by Serenity ThompsonDetails: santlouHi,I maintain many REXX Execs that streamline development tasks. We are in a Mainframe z/os COBOL environment. One tool that I developed is an ISPF Edit Macro that allows the developer to 'BookMark' several locations in a source component to allow him to quickly access the BookMarked location later. The Edit Macro simply stores the Datasetset Name, Member Name, and current ISPF EDIT LineNumber in an ISPF Table for later use.The use of an ISPF Table allows the BookMarks to be persisted over future ISPF sessions. This tool is very helpful when deveoping a Large Cobol Source and is widely used in our development community. However, using Changeman to edit source code poses a bottleneck when bookmarking.When a component is selected for Edit in Changeman, a dynamic Temporary dataset name is created for the edit session. Thus whenever the bookmark feature is used, it cannot be persisted because the Changeman Edit dataset name

I'm wondering if anyone except us use the XML REXX interface to Changeman ? Seems that we that do will benefit of exchange of experience.#REXX#XML#ChangeManZMF

Status: DeliveredThis has been completed in ZMF 8.3 CR 135018 Ideas -Show component description in component listsShow component description in component lists We use the "Component Description" field to give a short specification of the component. Unfortunately CHangeMan does not show this description in any component list, e.g. if you browse the baseline or enter your package with "S2". It can be very circumstantial to find the component someone is searching for if they don’t know the exact name. So we suggest that the "Component Description" field is shown every time components are listed. For example if you check out a component from baseline, browse the baseline or list your package.

Question posted 3/2/09 by Gary RubbertDetails:We have applications that use DB2 tables in multiple regions. Some programs need to be bound to DB2A, while others need to be bound to DB2B. The programs are in one baseline library (SRC), and all create LDB and /or LDC, and DBR library types out of the compile.*The goal is to bind programs only where and when needed.What are our options? Trying to automate and not seperate the SRC by DB2 regions.#ChangeManZMF#oldforumpost#post3cf4c74d5a

Another customer issue that pops up from time to time is the inability to obtain a dump from the CMN ZMF ISPF client.  The actual abends can be unexpected or deliberate and related to issues within the product, environment or customizations.   So, how can we get something more useful out of ZMF than messages such as “Abend 0C4000 hex occurred processing command 'CMNINIT '.”?    The slightly unusual thing about this issue is that since the ability to capture a dump in this situation was significantly simplified in ZMF 6.1.0, the default setting in our sample code has been to always enable the dump capture processing.  However, for a variety of reasons, it appears that some customers may have missed or deliberately disabled this default.  So, let’s take an example and work through it. In our example, whenever a user attempts to edit any package component:   The request always results in the following failure: So, what does this tell us?  To

ZMF 8.1 and ZMF Client Pack 8.1 Documentation Delivery Schedule The following table identifies the quarterly delivery schedule for updates to ZMF and ZMF Client Pack documentation at the 8.1 release level. You can download the documentation for ZMF 8.1 and the ZMF 8.1 Client Pack from the Download area of the Serena Support Web site at: http://support.serena.com/Download/Default.aspx. You will need a user ID, password, and authorization or product license to access the ZMF and ZMF Client Pack product at this location.     ZMF 8.1 and ZMF Client Pack 8.1 Documentation Delivery Schedule Document Availability Schedule ZMF Installation Guide Completed; available. ZMF 8.1 Migration Guide Completed; available. HLLX Getting Started Guide Completed; available. ZMF Administrator’s Guide Completed; available. ZMF 8.1 Readme Completed; available. ZMF Quick Reference Completed; available. ZMF User’s Guide Completed; available. ZMF Cu

With the introduction of Resource Access Control Facility (RACF) in 1976, ACF2 and Top Secret Security shortly thereafter, and their evolutionary path into z/OS security servers, these External Security Managers (ESMs) have provided tight controls around authentication and access control that have advanced to support for X.500 series, digital certificates, the ability to administer, store, use and export keys, with a notable uplift in security around mobility, analytics and the cloud.     However, mainframe security goes beyond access control. As has been pointed out many times in many publications, without the underlying system integrity (see IBM’s z/OS System Integrity Statement), access control can be bypassed and therefore access can be gained to about anything in the environment while bypassing the ESM, audit trails and SMF recording.   As sophisticated as today’s mainframe security mechanisms are, there are still vulnerabilities. Mainframe security and system

  If you are part of the ChangeMan ZMF community, you may have received the ChangeMan ZMF Product Survey which went out in February of this year. If you were at xChange 2015, or if you’ve been on the last couple of Mainframe VUGs (Virtual User Groups), you have heard Mark Levy and I mention the survey. During the kickoff session of the Mainframe track at xChange, among other topics such as the product roadmap, product futures and initiatives within R&D, I presented a glimpse of the survey results. The survey was still open so the results weren’t finalized but were consistent and in-line with what we are seeing now that the survey is closed. The results follow.   2015 demographics (questions 1 & 2)   Industry    Job function   Business Services 1.72% Developer 5.17% Consulting 3.45% ChangeMan ZMF admin 65.52% Finance: Banking 29.31% Change/Config manager 10.34% Finance: Insurance 24.14% Ot

This video outlines the need for, and support of, passtickets in ChangeMan ZMFA security review found there was room for improvement in the authentication of mainframe-based clients connecting to ChangeMan ZMF via TCP/IP. The answer was to adopt IBM's Secured Signon Function and passtickets.#Announcement#HowTo-BestPractice#Videos#ChangeManZMF

Introduction  Amongst the most common type of issues reported to Serena Support’s ZMF team are problems related to ChangeMan ZMF security profiles.  It is reasonably common for us to discuss “Dave being unable to see or select the admin option” or “Heidi not being allowed to create a package in application TOGA”.  So, how do we go about researching such a problem and can customers perform any self-diagnosis of such issues?  Obviously the answer to the latter is ‘yes’ or this would be a very short blog entry.  So, let’s use an example and work through the diagnosis process.    Description  Our sample situation is that user CMNSUP1 on our ZMF 8.1 subsystem id 4 cannot access the admin option.  When they logon to the ZMF ISPF client they see the unavailable ‘A  Admin’ option but when they attempt to access it they receive the standard error messages: However, our Security Administrator is also telling us that they have granted access to

In a Galaxy far away there is a place for clones to do the job over and over again.  But alas they are flawed without a heart and soul they can not grow up they cannot evolve into the next generation of fighting machines..   At least not like the original that is delivered from the factory.   When the upgrade is announced it is difficult to find the wretched clone because they can have any name the master of the day gave them.  So they are lost for ever to be many releases behind their coworkers inefficient and possibly totally forgotten In the real world reuse is accomplished by augmentation and adaptation and not by cloning the delivered code. What the creator of ChangeMan ZMF has done in the latest releases is make it possible for you to almost never change a delivered skeleton except for ones that are set up specifically for that purpose.   The most common cloned skeletons are the compilers -- the least required custo