Knowledgebase
Home
>
Results
Find Answers
Filter Search Results
All Operating Systems:
All Others
(12)
All Products:
Comparex
(47)
All Solution Types:
Documentation Update
(3)
Installation & Customization
(6)
Product Tips & Advice
(16)
Source:
Defects
(23)
Solutions
(24)
Ask a Question
Search
Example: "Database could not be verified"
Tips
|
Start Over
|
Solutions
|
Alerts
|
Patches
|
Defects
Pages [
Next
]
Results
Sample COPYBOOK and data for COPYBOOK and COPYLIB Parser
Sample
COPYBOOK and data for COPYBOOK and COPYLIB Parser
sample JCL for excluding a module during a compare
sample
JCL for excluding a module during a compare
Sample JCL for compiling and linking CPX$ISPF?
Sample
JCL for compiling and linking CPX$ISPF?
Sample of REXX exec for invoking M+R from CPX 8.5.0
Sample
of REXX exec for invoking M+R from CPX 8.5.0
Sample CPX870 REXX EXEC should have hardcoded data sets removed
Sample
CPX870 REXX EXEC should have hardcoded data sets removed
CPX870: LICTEST sample JCL has product code=100 when 101
CPX870: LICTEST
sample
JCL has product code=100 when 101
SERUPDTE and CPXVB2FB assembly and linkedit JCL
Does
sample
JCL to assemble and link members SERUPDTE and CPXVB2FB in CPX.IFACE exist?
Comparex 8.7 LICTEST utililty. Incorrect product ID
The product ID for Comparex in the comments of the
sample
JCL is listed as 100.
It should be 101 starting with this version.
Use of KEY parameter with data compare (as in POSTINST job) results in incorrect results
If using the KEY parameter, data compare can result in the last record not compared.
Sample
of the control parameters can be found in the CPX.IFACE(POSTINST) job.
Refer to DEF296274 for a detailed description of the problem.
S0C4 in COMPAREX processing csects in PDSE to PDSE compare
Performing a pdse to pdse compare using the following parameters, a S0C4 results.
Sample
JCL
//COMPAREX EXEC PGM=COMPAREX
Pages [
Next
]
Welcome kb sso
My Profile
My Subscriptions
My Recent Searches
cor4501250E
disable port 80 binding
specific client version
Saving Varrecord Objects Failed, but process app changes were committed
Licensed number of users already reached
ORA-00904:
Search Feedback
Are we answering your questions?
No
Yes
Submit
Additional Assistance
Submit a Case Online
Give us Your Feedback
FAQs