Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML ZMF4ECL: Issues creating new, non-zFS components with lower case characters
When testing here the request completely disappears. No response is ever received and no errors appear on any log . In the customer's environment they receive a CMN6504I message but the member is created and appears to exist in the package.
CMS-XML Avoiding S0c4's in VSAM for package/component master, recovery, log and other VSAM files especially during times of high number of Change Man users (including batch jobs)
This represents the number of request parameter lists or RPL's that can be used concurrently for that VSAM dataset. Each user causing I/O to a VSAM dataset (package master or log file) will use an RPL. If the number of users is greater than the specified STRNO, dynamic RPL's will be acquired. In some cases , associated control blocks used by VSAM are freed during usage of the dynamic RPL and abends will occur attempting to reference one of the associated control blocks (IOPLH).
CMS-XML ERO: Component checkin message truncated in log file
A log record is generated when checking a package into a release area. However, in many cases the package name is physically truncated in the record thus making it inaccessible through any display mechanism (e.g. via online ISPF, in batch, through XML Services, etc.).
CMS-XML Inconsistent logging of package approval requests
The behaviour of the online processing has been traced back from as far as 5.3.6. However, from the description shown to customers viewing the log ('20 Approve a Package'), and lacking any documentation stating that this is only designed to list final approvals (which may or may not be the case ), the current services processing would appear to be working as documented.
CMS-XML Sernet Activity Log and monthly reporting feature.
A8. No, but it will not hurt to do so and recover them in case DR is required. See also Q9.
CMS-XML ZMF Plugin: rlc.log gives error " xxxxx"
Open the RLC Provider Admin ( http://SbmServer:80/workcenter/tmtrack.dll? shell =swc&StdPage&Template=rlm/provideradmin ) Update the ZMF Configuration. Update the Mainframe Connector URL as needed.
CMS-XML ZMF Plugin: Tomcat localhost.log gives error " ?xxxxx"
Open the RLC Provider Admin ( http://SbmServer:80/workcenter/tmtrack.dll? shell =swc&StdPage&Template=rlm/provideradmin ) Update the ZMF Configuration. Delete everything from the ZMF Server field and re-type it.
CMS-XML S23E abend for TSO session cancelled from ZMF with LBO
If a user is logged onto ZMF using the Load Balancing Option and the session is cancelled, the user gets an S23E abend. In some cases the abend is written to the system log , but always to the user's TSO session.
CMS-XML CLEARLOG ends with RC=12 for minimally used ZMF systems
In the vast majority of cases this will work fine and there will be at least a ZMF termination record contained in the log dataset. However, for test systems especially, it is possible that they may be down for an extended period of time meaning that no log records exist in the log file. Running the new CLEARLOG process in this situation it is possible that this could fail with a RC=12 in the AGEBACK step accompanied by the following type of IDCAMS output:
CMS-XML 'CMNALLIO unable to read/write logfile' during admin update
Change Man, in this case CMNADMIN, issues a LOG request, and all it knows is that something on the VSAM level went wrong. It is not feasible to check for everything that could possibly happen, especially since VSAM itself treats a full data set as some kind of I/O error and is not intelligent enough to know that the data set is full.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs