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
PDF RLM HTTP Server Overview:
... directory can be found under the “ ... ... auto-deployment is not set, the ... <security-constraint> <web-resource-collection> <web-resource-name>RlmServlet</web-resource-name> < url -pattern>/*</ url -pattern> </web-resource-collection> <user-data-constraint> <transport-guarantee>CONFIDENTIAL</transport-guarantee> </user-data-constraint> </security-constraint>
CMS-XML Unable to execute a command line using Ext.CmdLineWait() function
When using Ext.CmdLineWait() in App Script, commands are executed in the context of the Internet Information Services (IIS) application pool. If the script is called from a transition or URL , the script runs under the application pool for the TMTrack virtual directory which defaults to DefaultAppPool. If the script is called from a notification in 10.1+, it will run under the gsoap_pool.
CMS-XML IBM Unicode Services Red Alert (APAR OA48941) and Serena Software Mainframe Products
(If this link does not work for any reason simply search for APAR OA48941 on the IBM Support website.) The following Serena Software mainframe products make use of these Unicode Services and will also be affected by this issue once host systems are IPL’d on or after December 15th 2015: - the ChangeMan ZMF Client Pack, including both the ChangeMan ZDD and ChangeMan ZMF for Eclipse (ZMF4ECL) products.
PDF Microsoft Word - ZMF ALF Event Filters for RLM.docx
... a package 42 No selective unfreeze 43 No demoted a component ... a package 49 No promoted a component ... a package 51 No change audit return ... release area 60 No link a package 62 No unlink a package 64 No scratch a component 66 No rename a component 68 No copied a component ... complete 79 Yes Retrieve from release area ... - create 81 No Check component into release area 82 No checkout to a package 83 No potential checkout conflict 84 No stage something 85 No overlay previous module 86 No delete module from package 87 No Checkout something from release 88 No copy forward package 89 No Retrieve component from release 90 No monitor 91 No generate release global information 92 No generate release information 93 No generate release appl ... to release 96 No link a release 97 No unlink a release
CMS-XML Product Lifecycle and Platform Matrix
The Product Lifecycle page lists each product release, its status and the end of support date. Start at the Product Lifecycle page. Search for you product in the dropdown list.
CMS-XML Notification links go to the SBM view not the ALM shell view
If you are using the ALM package with SBM, the notification links will take you directly to the regular SBM view of a record. NOTE: Beginning in SBM 10.1.2, the URL link will go to the ALM shell.
CMS-XML ALM Connector: RestGrid using /almzmfws/services/SernetProxyHttpServer gives: Unknown error received 500
Unknown error received from https://XXXXX/sbmproxy/xhp [ url : 'http://XXXXX:8080/almzmfws/services/SernetProxyHttpServer?system=ZMF&hostName=999.999.999.999&hostPortId=999&userId=XXXXX&responseType=JSON&request=PACKAGE%2FGENERAL%2FSEARCH%2Fpackage%3D*%2
PDF Serena Application Release Manager Installation and Configuration Giude
ChangeMan ZMF can be configured to retain audit reports in compressed printable ZMF format and in HTML format in a package staging library on the mainframe. The HTML- formatted reports can then be retrieved by ARM for viewing in the Work Change Request (WCR) workflow under the ZMF Info tab.
CMS-XML Mainframe Connector Extensions: Mainframe Configuration for accessing ChangeMan ZMF from SBM
Configure the NTFYURL; this is the URL SBM uses to send information to SERNET through the server. See Configuring the Notification URL and the related topic, ChangeMan ZMF Event Handling .
CMS-XML ARM 1.2 Hotfix for ZMF 5.6.3 Compatibility
was created using TSO XMIT. In order to properly unload it on your mainframe, you must upload the file using the binary transfer method, and unload it using the TSO RECEIVE command. Detailed instructions are found in the document titled $receive.doc.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs