Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Setting ZMF user panel names in panel logic (e.g. CMNUSR01)
Setting ZMF user panel names in panel logic (e.g. CMNUSR01 )
CMS-XML Issues corrected by fix for DEF289980 cause panel validation errors on panel CMNUSR01
Issues corrected by fix for DEF289980 cause panel validation errors on panel CMNUSR01
CMS-XML BULD01US cursorField '069' goes to wrong position on panel CMNUSR01
BULD 01 US cursorField '069' goes to wrong position on panel CMNUSR01
CMS-XML CMNSTG04 ignoring ‘OTHER OPTIONS’ setting when &USRPAN not set to CMNUSR01
CMNSTG04 ignoring ‘OTHER OPTIONS’ setting when &USRPAN not set to CMNUSR01
CMS-XML Panel process changed between panel CMNSTG04 and display of panel CMNUSR01 when you PF3 out of CMNUSR01
Panel process changed between panel CMNSTG04 and display of panel CMNUSR01 when you PF3 out of CMNUSR01
CMS-XML Changing data in HLLX BULD0002 sets member name to CMNUSR01 on CMNSTG02
Changing data in HLLX BULD0002 sets member name to CMNUSR01 on CMNSTG02
CMS-XML HLLX: Unable to set cursorField to component user variables on CMNUSR01
HLLX: Unable to set cursorField to component user variables on CMNUSR01
PDF ChangeMan ZDD 7.1.3.01 Server Installation Guide
 Field labels, edit rules, and default values for the ZDD client Build dialog. This dialog is the equivalent of the ISPF staging panels and the User Option Panel ( CMNUSR01 ).
CMS-XML UV command and user panels
The USRPAN variable in the panels is used by customers to display a different user panel based on libtype, appl, proc, etc. But, when the UV command is issued, the default CMNUSR01 panel is displayed and users can update the variables. The variables on CMNUSR01 can be completely different than the variables in the custom panels.
CMS-XML Component user option data being inadvertently folded to upper case
A customer uses the component user option fields to host case sensitive data. When switching between selecting and de-selecting both the CMNSTG04 ‘Other options’ and CMNUSR01 ‘Mixed Case’ fields the contents of these fields can be inadvertently converted to upper case, even when the user options panel (e.g. CMNUSR01 ) has not been displayed.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs