Browse all forums dedicated to the Rocket Mainframe DevOps product family.
Recently active
Status: Waiting for VotesWe run housekeeping every night, so that only the latest 10 staging versions are kept for each package. There is no way of maintaining this by application. Ideally we would like to keep the latest 20 staging versions for some applications.#ZMF
Hello, The Copybooks and Includes are downloaded but not displayed as available. Is there a setting in IBM Z Open Editor to be made, to be able to open the copybook? ZMF has the Option to download the Copybooks, and I get the message that they were being downloaded: But I still get the error message: what could I do to fix the issue?#ChangeManZMF#Copybookresolvement#VSCode#include#ZMFExplorer#COPYBOOKS#ZMF#VSCode
Hi, I'm testing ChangeMan REST API functions from zmf plug in for zowe cli using the sample from Trigger DEMOTE outside the mainframe using Jenkins Pipeline I've a problem with returned json. Just executing the command zowe zmf get component -c "PYTCC001" -t "COB" -p "BKA 000435" --zmf-profile "zmfx" > K:/projectsout/mainframe/cmnrestsample/testhttp.json from a Windows Command line (Powershell, cmd, ...) I get a text file with many "dirt" chars. I've tried also a direct connection to Tomcat using only http port but nothing Changes. Returned json is something like this where expected json fields are surrounded by these wrong chars: Somebody has an idea where to investigate? Thanks. #problem#JSON#ChangeManZMF#CLI#REST#ZMF
PKIX refers to ‘Public Key Infrastructure (X.509)’ and errors referring to PKIX may be experienced in various java-based ZMF interfaces when attempting secure (i.e. SSL/AT-TLS) connection between entities/applications. For example, the following message may be reported when attempting a ZMF4ECL connection to a ZMF Server that has the ‘Connections Secured via TLS’ option specified: Connect Error: PKIX patch building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find Valid Certification path to requested target Or this type of error could be seen in the ZMFREST output file of a tomcat task when attempting to create a secure dialog with a Jenkins server: javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.j: PKIX path building failed: com.ibm.security.cert.IBMCertPathBuilderException: unable to find valid certification path to requested target As suggested by the text in the above messages, these PKIX errors indicate that the java environment cannot fin
Hello, We are able to trigger the demote process by using the Skeleton inside the mainframe without issue. However, application team would like We have a User that is looking to create a Jenkins pipeline that will be initiated by a Package Promote on ZMF. The pipeline will execute a test off-mainframe and if the results are bad, they wish to initiate a Package Demote from the same pipeline. We know how to post an event from the mainframe via skeletons, but how does this work in the other direction. We are looking for code examples to execute the Package Demote(or any REST service) from a Jenkins script. Thank you! David#Webservices#jenkins#ChangeManZMF
Hello, We have some problem with the ZMF Explorer plugin in VS-Code:some users see the "right click" create package, some others can't.The users which are unable to see the option to create a Package, can see the Package list itself. All those users of course are able to create packages from 3270 ISPF interface.This is what users should see. In the picture the user has the ability to see all the packages for application CM# but no package for application BKA.For some applications, some users can see the full list of the packages, some others (see the picture) will not see anything. Notice: the user that is not able to see BKA packages list is the ChangeMan administrator so RACF is for sure ok. We set up the debug level but we cannot see anything in zmfExplorer.log nor in the Tomcat started task nor in ChangeMan started task. Could it be something related to the UI in VS-Code? Is there a "debug" for the UI related to ZMF Explorer? Notice: no filter is used. When no packages are displa
ChangeMan ZMF 8.3 is the first release to ship all components in PDSE format. Releases prior to 8.3 shipped product libraries in PDS format. However, for a number of years hotfixes supplied for all releases have been shipped in PDSE format. This can lead to users encountering the following type of error when attempting to TSO RECEIVE a PDSE-formatted hotfix executable module (i.e. program object) directly into a PDS-formatted execution library: INMR060I RECEIVE command terminated. Output dataset unusable. + INMR158I A Program Library or member can only be received into a Program Library or an empty PDSE.*** To circumvent this issue users can either receive the hotfix directly into an existing PDSE or omit the target dataset entirely and allow the TSO RECEIVE command to allocate a new PDSE to host the new or updated component(s). The received program objects can then be copied to the required target PDS dataset using IBM utilities (e.g. ISPF option 3.3, IEBCOPY, etc.).#SupportTips/Knowl
We are trying to clone the GitHub repository in mainframe using Git Clone command. but facing 403 error while cloning. fatal: unable to access '
Trying to `git clone` from a repository on another z/OS system I get$git clone -v demnt15@stutvs2a:/u/demnt15/tmp/mytestCloning into 'mytest'...fatal: protocol error: bad line length character: ����fatal: the remote end hung up unexpectedlywhere the characters are <<^ 88D0CCD6I have no idea why this happens. Any advice would be appreciated. If I try to clone from WSL in Windows I get the same error.------------------------------Manfred LotzKyndryl Deutschland GmbHKelsterbach DE------------------------------
Hi, I have curl 8.4.0 with z/OS 2.4 and I am getting these errors: OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to xxx.xxx.xxx.xxx:443 On the first request if failed with insufficient randomness, which points to /dev/random and /dev/random not working correctly, which led me to find out CSF was not started and the SAF resources was not defined. We got past that, the User ID using Curl has READ access to the following CSFSERV profiles : CSNBRNG - Random Number Generate CSFNRNGL - Random Number Generate Long Now, is there any other profile that needs to be authorized for SSL to work ? I did peek the documentation and I could not find any references. curl -V curl 8.4.0 (i370-ibm-openedition) libcurl/8.4.0 OpenSSL/3.1.4Release-Date: 2023-10-11Protocols: dict file ftp ftps gopher gophers http https imap imaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftpFeatures: alt-svc AsynchDNS HSTS HTTPS-proxy Largefile NTLM SSL TLS-SRP UnixSockets
Has anyone added support for python in ChangeMan ZMF?#ChangeManZMF
The ALFFLTR member delivered in the distributed ZMF SAMPLES library lists all default log events that will be delivered to the NTFYURL address for processing. As explained in this member itself, all of the listed events are delivered commented in this member which results in all of them being emitted to the NTFYURL software (e.g. tomcat, SBM, etc.). Care needs to be taken when changing or uncommenting any single event in, or adding an additional, non-default event to, the ALFFLTR dataset/member. This will result in ONLY the uncommented events being sent. All other events that were formerly sent by default will automatically be disabled in this situation.#ALFFLTR#ChangeManZMF#SupportTips/KnowledgeDocs#NTFYURL#ZMFRESTAPI
A new hotfix build of ChangeMan ZMF for Eclipse (ZMF4ECL) 8.3, ZMF4ECL 8.3.0 Hotfix 006 (build 690), is now available for customer use. This build resolves several issues, including the following: OCTCR46A367001 - Invalid message "Baseline level invalid - No response from ZMF" when Baseline Compare This latest hotfix build is cumulative with earlier hotfix builds and therefore includes the changes included in all of these, too. We recommend customers either running or upgrading to ZMF4ECL 8.3 open a case with the Support team requesting a copy of the latest ZMF4ECL hotfix build.#SupportTip#ChangeManZMF#SupportTips/KnowledgeDocs#Announcement
We have already posted a Support Tip reminding customers of the need to rebuild all ZMF assembler exits (i.e. custom CMNEXnnn modules) when upgrading across the 8.3 release in the following post: Support Tip: Remember to rebuild all assembler exits when upgrading to ChangeMan ZMF 8.3+ It is also important to note any significant changes to the supplied sample exits or copybooks that they use when upgrading the product. For example, customers who use the X09@ADSC table within CMNEX009 to add approvers to packages must note that up to and including the 8.2 Patch 7 release each table entry consisted of 90 byte records: ... X09@ADSC DS 0CL90 approver description table DC CL3'JCL' library type DC CL8'JCLCHECK' security entity name DC CL44'JCL Checker' description DC AL2(0002) hierarchical order number DC AL1(X09$M
In June 2023 we published the following Support Tip that contained maintenance which we recommend customers install prior to upgrading to the ZMF 8.3 release: Support Tip: Recommended maintenance for customers running or upgrading to ChangeMan ZMF 8.3 This was followed in August 2023 with the following article detailing additional changes that we recommend customers install prior to their upgrade: Support Tip: Further maintenance recommended for customers running or upgrading to ChangeMan ZMF 8.3 Recently a further issue has come to light that, again, we recommend customers resolve prior to upgrading the product. This is critical for customers that use ‘Save Staging Versions’ (SSV) functionality: SSM8.6.1.003/OCTCR46A339001 Users receiving CMN8711I errors after upgrade to ZMF 8.3 As always, the same notes, caveats, etc., as before apply to the above recommendation. Namely: a. All of the issues listed above, and their associated hotfixes, apply to the
Several articles have been published over the last year referencing maintenance we deem as high priority for customers moving to the ZMF 8.3 release. These follow: Support Tip: Recommended maintenance for customers running or upgrading to ChangeMan ZMF 8.3 Support Tip: Further maintenance recommended for customers running or upgrading to ChangeMan ZMF 8.3 Support Tip: Additional maintenance recommended for customers upgrading to ChangeMan ZMF 8.3 (September 2023) We recently diagnosed and produced a hotfix for a newly reported problem that falls into the same category. Customers running or upgrading to ZMF 8.3 and who use the default LDS mechanism to house their Impact Analysis (I/A) table should familiarise themselves with the problem documented in the following KB article and follow the instructions supplied to request the hotfix: ZMF 8.3.0.038/OCTCR46A377001 Impact Analysis table-related functions failing without explanation As always, the same notes, cav
Hi, We have installed DSFS.When I `cd` to a PDS and do a `sed -i ...`,sed wants to create a tmp file in current directory, however,this tmp file is not a valid member name. Would be nice if someon could write a path, that would make sedcreate the tmp file in fx /tmp. myUSER@myMVS:~$ sed --versionsed (GNU sed) 4.2.2Copyright (C) 2012 Free Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.This is free software: you are free to change and redistribute it.There is NO WARRANTY, to the extent permitted by law. Written by Jay Fenlason, Tom Lord, Ken Pizzini,and Paolo Bonzini.GNU sed home page: <http://www.gnu.org/software/sed/>.General help using GNU software: <http://www.gnu.org/gethelp/>.E-mail bug reports to: <bug-sed@gnu.org>.Be sure to include the word ``sed'' somewhere in the ``Subject:'' field. myUSER@myMVS:~$ cd /dsfs/txt/myuser/clist myUSER@myMVS:/dsfs/txt/myuser/clist$ sed -i 's/a/b/' bsed: couldn't open te
Following the instructions in the “Release notes for Git 2.3.5 for zOS.pdf” for “Cloning an open source repository” I get the following error: git clone -v git@github.ibm.com:matthew-webster/hello-world.git Cloning into ‘hello-world’… error: cannot run index-pack: EDC5129I No such file or directory. CEE5205S The signal SIGTERM was received. fatal: fetch-pack: unable to fork off index-pack Can anyone tell me what I have not configured correctly? Thanks in advance
Status: DeliveredThis change is now in the code base which will form ZMF 8.3patch1 Is it possible to add the bind parameter APPLCOMPAT in the TOKEN processing ACQUIRE CACHESIZE COPY CURRENTDATA CURRENTSERVER DBPROTOCOL DEGREE DISCONNECT DYNAMICRULES ENCODING EXPLAIN FLAG IMMEDWRITE ISOLATION KEEPDYNAMIC LIBRARY MEMBER OPTHINT OWNER PACKAGE name PATH PKLIST PLAN name QUALIFIER RELEASE REOPT REPLVER ROUNDING SQLERROR SQLRULES VALIDATE These are the Bind Parmenter's that are currentley supported, #ReduceCustomizations#ZMF
It is worth stressing that whilst ChangeMan ZMF Enterprise Release Option (ERO) release packages are fully aware of base ZMF package behaviour, the opposite is not always true. The additional functionality provided by ERO results in a potentially more complex component build configuration that several ZMF functions, including package audit processing, cannot understand. Due to this, the ZMF package audit function is limited to automatically enabling the ‘Audit staging libraries only’ option when running against an ERO release package. The package audit AD000/PGM=CMNAD000 step issues the following information messages in the SYSPRINT output file to explain this behaviour: CMN2614I - Package is attached to a Release, package audit processing will be restricted to staging contents.CMN2617I - Use ERO Area Audit to ensure integrity across the release areas and baseline. Further information, including a list of the package audit SYNCH! errors that will NOT be reported in this situation, can
Status: DeliveredChanges have been made to deliver this requirement and the changed code will be seen in ZMF 8.3 patch1. REXX exit users will not need to change anything, the REXX longMsg variable will now allow for up to 512 bytes of usable data (you can put as much as you like into longMsg but only the first 512 bytes will be used). LE exit users will have to, at minimum, recompile their exits to pick up changed copybooks supplied with ZMF 8.3 patch1. If LE users have no need of messages longer than 128 bytes they can continue to use the existing xxxxLONG fixed length fields. If they need more room then they must put a blank in the xxxxLONG field and then proceed to use the new xxxxXLON varchar fields which will accept up to 512 bytes of data. Note: all HLLX functional areas have been addressed. I'm in the process of finally getting the remaining ISPF panel customizations converted over to use HLLX. The "shortMsg" variable is 25 character in length, which matches the leng
youtu.be/hhoUSv2lOGE#Videos
It is not always obvious to customers exactly where the initial attributes assigned to ERO Release Area datasets are defined. This information may be accessed in the following manner: Select ISPF Option A (Admin) – R (ERO) – A (Application). List the release. Use line command RA to display applications joined to this release. Enter line command AL to list the library types. Enter line command QL to display the default allocation settings or UL to update them. Note: The library type allocation characteristics will only apply BEFORE the area dataset is created. Although updates to the definition panel may be allowed after this point, the dataset will already have been allocated and users will often see the following type of message issued in this situation: Not All Changes Allowed/CMR5502A - Library Type(s) JCL area libraries already allocated. Further information on allocating release area library types may be found in the section entitled ‘Define Application Library Types’ in the Cha
A new version of the ChangeMan ZMF plugin for zowe cli V2.0.5 now exists in the OpenText Marketplace An new version of the VSCode ChangeMan ZMF Explorer V2.0.5 is now available on the VSCode MarketPlace. Please note that these will be the final version to support Zowe V2. Zowe V3 is due to be released GA at the end of March at which time, we expect to release V3.x of these compatible products. #ChangeManZMF#Announcement#NewRelease-Feature
Hi Team,Do you know if the Rocket filesystems need to be one set per LPAR or can they be one set per shared SYSPLEXThey are currently mounted as Read/Write. I need to know if they can be mounted as READ.Regards,Ram------------------------------Ram Kumarz/OS system programmerFiserv Incomaha NE US------------------------------
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.