31
z/OS Server / Re: CMOD 9.5 (maybe 10) and OSPROTECT?
« on: January 18, 2019, 08:25:25 AM »
Nice Ed! 
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
32
z/OS Server / Re: CMOD 9.5 (maybe 10) and OSPROTECT?
« on: January 18, 2019, 07:29:19 AM »
It sounds like you are calling a library that is not APF authorized. Do you have an exit that is not in an APF authorized library?
33
Windows Client / Re: Send (File Menu) OnDemand Client v9.5.0.3
« on: December 31, 2018, 12:55:21 PM »
Ed, that is interesting. I was just starting to package the V10.1 64 bit client and had not done the email test yet. I started it up and the send option is not greyed out but it fails to detect a mail client and suggests I set a default. Guess, I will download the 32bit client instead. Thanks for sharing.
34
z/OS Server / Re: ARS0430E
« on: November 06, 2018, 05:50:39 AM »
I am not certain what 14 is but the best course of action is to search the system log on Z/OS in SDSF or in the daily dataset file if it has rolled off. Most often you will find an OAM or SMS message that is explaining why the object dataset failed. Search the logs for the name of the storage node that is being used.
35
z/OS Server / Re: CMOD Migration from Z/Linux to AIX
« on: October 20, 2018, 09:10:59 PM »
I have read the question several times and it doesn't make sense to me. Can you please detail more of what your current set up is and what you want to move to? Are you asking about switching from IHS on Z/OS to apache on AIX? What is on zLinux? The OnDemand instance? 
36
z/OS Server / Re: SSL on z/OS
« on: August 27, 2018, 01:29:46 PM »
I have had a few more bumps on this ride.
We are using internal certificates and the GSK8 is not handling the chain of certificates. For some reason, our ROOT is not marked critical for BasicConstraints extension and our intermediate is. Not sure yet how to resolve that. Hoping the PMR will advise how to handle it.
I did revert to a Self Signed certificate using the gskkyman method. Following that, I was able to setup SSL from the client to the server successfully.
Note in Step 2 in the guide, it is missing instructions to create the stash file.
From the main gskkyman pannel do 2. Open DB, enter the db name, enter the password, select 10 to store database password.
It will display the path and file name of the stash file required for your ars.ini in Step 3.
Now, I have a problem with my remote loading of PDF documents where it is now picking up extra characters to the AG name causing it to fail. Will start looking at the local report specification exit.
We are using internal certificates and the GSK8 is not handling the chain of certificates. For some reason, our ROOT is not marked critical for BasicConstraints extension and our intermediate is. Not sure yet how to resolve that. Hoping the PMR will advise how to handle it.
I did revert to a Self Signed certificate using the gskkyman method. Following that, I was able to setup SSL from the client to the server successfully.
Note in Step 2 in the guide, it is missing instructions to create the stash file.
From the main gskkyman pannel do 2. Open DB, enter the db name, enter the password, select 10 to store database password.
It will display the path and file name of the stash file required for your ars.ini in Step 3.
Now, I have a problem with my remote loading of PDF documents where it is now picking up extra characters to the AG name causing it to fail. Will start looking at the local report specification exit.
37
z/OS Server / Re: SSL on z/OS
« on: August 20, 2018, 06:26:09 PM »
Thanks, I had also seen that thread but -ca true gives invalid parm. The option -trust enable is what I used but it is now deprecated.
It does list it in the details that ca = true
basicConstraints
ca = true
pathLen = 1633108
PMR opened. Will let you know when I find the solution.
It does list it in the details that ca = true
basicConstraints
ca = true
pathLen = 1633108
PMR opened. Will let you know when I find the solution.
38
z/OS Server / Re: SSL on z/OS
« on: August 20, 2018, 12:42:43 PM »
I had added them; RBC.ROOT and RBC.INT1/2 were supposed to create the trust chain. When I run the validate commands
ROOT: validates ok.
INT:
CTGSK2052W An invalid basic constraint extension was found.
CTGSK2052W An invalid basic constraint extension was found.
Google hasn't helped me figure out how to fix it.
I opened a PMR, hoping for help there
ROOT: validates ok.
INT:
CTGSK2052W An invalid basic constraint extension was found.
CTGSK2052W An invalid basic constraint extension was found.
Google hasn't helped me figure out how to fix it.
I opened a PMR, hoping for help there
39
z/OS Server / Re: SSL on z/OS
« on: August 17, 2018, 12:26:23 PM »
It was going smoothly, till I tried to log in! I get 'Connection cannot be established ....' with no messages in STC or system log table.
ars.ini
SSL_PORT=1446
SSL_KEYRING_FILE=ssltring
SSL_KEYRING_LABEL=PP1TSERV_TEST
SSL_CLNT_USE_SSL=0
List of Cert in ondemand.kdb (we have internally trusted certs, so I added them to the db)
! RBC.ROOT
! RBC.INT1
! RBC.INT2
! PP1TSERV_TEST
Client
Use Secure Sockets Layer is enabled.
Any suggestions on how I can trace what is not set up right?
Thanks
ars.ini
SSL_PORT=1446
SSL_KEYRING_FILE=ssltring
SSL_KEYRING_LABEL=PP1TSERV_TEST
SSL_CLNT_USE_SSL=0
List of Cert in ondemand.kdb (we have internally trusted certs, so I added them to the db)
! RBC.ROOT
! RBC.INT1
! RBC.INT2
! PP1TSERV_TEST
Client
Use Secure Sockets Layer is enabled.
Any suggestions on how I can trace what is not set up right?
Thanks
40
Report Indexing / Re: PDF Page Piece info - help
« on: August 13, 2018, 12:18:01 PM »
Rereading your original post makes me wonder how you are 'merging' your PDFs into one file. It sounds like the tool you are using is not really merging but just concatenating the PDFs. I suspect that is what is throwing the indexer off. I haven't used such tools so I can be sure but I believe the recommendation from Bud is that the source application should create 1 large PDF document with the PPD details to allow for the maximum compression.
41
Report Indexing / Re: PDF Page Piece info - help
« on: August 09, 2018, 09:30:34 AM »
Two comments. You should patch up to 9.5.0.10 and I am certain that PDF indexing on Z/OS is not supported at V9.5. You should be running the PDF indexing on a Windows or Linux box and pushing it in to the Z/OS server.
42
Report Indexing / Re: PDF Page Piece info - help
« on: August 09, 2018, 06:06:51 AM »
I still think you need to try running the load with Compression turned off in the Load tab of the Application id. We also had that issue of increasing storage size but that was back on Z/OS.
43
Report Indexing / Re: PDF Page Piece info - help
« on: August 08, 2018, 05:28:26 PM »
If I remember what Bud said, you should not have compression enabled. PDF is already compressed so try turning it off and run your tests again.
44
z/OS Server / Re: SSL on z/OS
« on: August 01, 2018, 10:18:42 AM »
Thanks all for posting this very timely guide. I am setting it up now in our shop and will advise of surprises or updates required.
The only thing I have noted is that my gsk8 exe files are in the bin path and the dlls are in the lib path. I had to copy the exe to the lib path to run commands.
The only thing I have noted is that my gsk8 exe files are in the bin path and the dlls are in the lib path. I had to copy the exe to the lib path to run commands.
45
z/OS Server / Re: CMOD Extraction of data
« on: June 26, 2018, 09:26:19 AM »
That is a pretty tall order there Glenn.
Extracting data from CMOD on Z/OS is a standard arsdoc query and then arsdoc get...for every single report.
Transfer it using your internal mechanisms for file transfers between Z/OS and your Linux server. (be careful of EBCIDIC data moving to Linux)
Loading it in to Linux would be an arsload or using a daemon depending on your setup.
Retention does not follow the data, you would need to define it in the new Linux CMOD database.
To complete this, I would recommend REXX scripts on Z/OS to automate the extraction, JCLs to control and transfer the files and the shell scripts to load. (all run in the same JCLs)
Extracting data from CMOD on Z/OS is a standard arsdoc query and then arsdoc get...for every single report.
Transfer it using your internal mechanisms for file transfers between Z/OS and your Linux server. (be careful of EBCIDIC data moving to Linux)
Loading it in to Linux would be an arsload or using a daemon depending on your setup.
Retention does not follow the data, you would need to define it in the new Linux CMOD database.
To complete this, I would recommend REXX scripts on Z/OS to automate the extraction, JCLs to control and transfer the files and the shell scripts to load. (all run in the same JCLs)