| |
Results |
|
Users’ ISPF sessions hang during promotion request using XMS connection
|
A customer reported that users attempting to promote several different packages in their newly upgraded ZMF 7.1.2 environment were hanging with the following message displayed on their screen:
|
|
|
|
ZMF DP task hanging after upgrade to z/OS 2.2
|
A customer has reported intermittent ZMF 8.1.1.01 Server task hangs after upgrade of their primary development system to z/OS 2.2. The hangs occur when multiple users are connected (i.e. it does not appear to occur at ‘quiet’ times) and the Server task must be restarted to clear the issue. At this time there is no clear indication that HLLX is involved despite some of the symptoms matching prior HLLX incidents encountered at other customer sites.
|
|
|
|
Invalid SER8207E message after upgrade from 7.1.3.03 to 8.1.2 caused by incorrect version of SERLCSEC
|
Eventually we tracked down the cause of this particular SER8207E message. The customer had inadvertently retained their 7.1.3.03 custom version of security module SERLCSEC rather than re-applying their customisations to the 8.1.2 version. This resulted in an invalid PassTicket value being passed to the Security Server and, in turn, user verification failed and connection to the started task was correctly refused.
|
|
|
|
Link step failing with RC=12 after upgrading to COBOL V5.1.1 for the Eztrieve programs
|
The customer just upgraded from COBOL V4.1.1 to V5.1.1 and now all the Link steps are failing with a RC=12, for just the Eztrieve components. After some testing the customer determined that if the &&LCT is commented out of the //SYSLIN DD in the Link step, the Link completes fine.
|
|
|
|
Unexplained TCP/IP connectivity issues to ZMF Server started task
|
A customer is reporting that since upgrading to ZMF 8.2 Patch 3 a number of their ZMF4ECL users are unable to connect to their ZMF Server started task at certain times. The failures to connect are linked
|
|
|
|
HTTP 500 error connecting to ZMF web services.
|
Customer has upgraded to ZMF4ECL 8.1.1 and applied the 8.1.1 war file and now is getting : (500)Internal Server Error !ENTRY com.serena.eclipse.zmf.core 1 0 2016-03-29 13:23:25.535 !MESSAGE Exception in ZmfServer: (500)Internal Server Error
|
|
|
|
ZMF Connector 6.1.2: retrieveReleasePackageComponents and retrieveReleaseComponents were moved to EROActionServices
|
If you are using these and upgrade from ZMF Connector 6.1.1 to later versions of ZMF Connector , now ALM Connector , you will need to adjust your implementation accordingly. Note:
|
|
|
|
Intermittent logon failures when connecting to ZMF Server started task from ZMF Connector
|
A customer is testing their ZMF 8.1.1.01 upgrade and encountering intermittent password failures for their ZMF Connector userid. E.g.:
|
|
|
|
DynaZip DLL's cause Sernet Connect to not initialize
|
These are working just fine for our products. If some other installation program decides to upgrade these to the next version, there can be a potential problems. This is because the DynaZip DLLs are not necessarily back-compatible much the same way as the Microsoft MFC DLLs are.
|
|
|
|
S0C4-10 CMNVCOMP+8184 running batch checkin requests after upgrade to 8.1.2
|
ChangeMan(R) ZMF CMNVSRVC - 8.1.2 CMNVSRVC RC=0000,MSG=USERID connected CMNVSRVC SYSIN: OBJ=CMPONENT,MSG=CHECKIN,PKN=APPL000636,
|
|
|
