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.


Messages - Ed_Arnold

Pages: 1 ... 6 7 8 9 10 [11] 12 13 14 15 16 ... 80
151
z/OS Server / Re: How can ARSYSPIN exploit ARS.PTGN exit ?
« on: April 13, 2021, 03:20:31 PM »
Reminder that ARSYSPIN calls ARSLOAD under the covers.

I knew there was a doc out there somewhere on this which includes a checklist:

ARS.PTGN not active for ARSLOAD - Question and Answer

https://www.ibm.com/support/pages/node/81145

Ed

152
z/OS Server / Re: How can ARSYSPIN exploit ARS.PTGN exit ?
« on: April 13, 2021, 12:12:30 PM »
Okay,

ARSYSPIN:  ARSUSER

ARSSOCD:  ARSUSER

> The configuration was done and it is working with no problem when I submit a JOB directly calling ARSLOAD application.

What userid is associated with that JOB?

Ed


153
z/OS Server / Re: How can ARSYSPIN exploit ARS.PTGN exit ?
« on: April 12, 2021, 01:39:12 PM »
When you submit the job what userid is it running under?

IRR010I  USERID ODLOADER IS ASSIGNED TO THIS JOB.

What userid is ARSYSPIN running under?

IEF695I START ARSYP1QA WITH JOBNAME ARSYP1BL IS ASSIGNED TO USER ARSSV100, GROUP ODCMARS

Ed


154
z/OS Server / Re: z/OS V2.3 Release Notes
« on: April 12, 2021, 01:05:58 PM »
CMOD exposes the following JES2 issue:

OA60092: STORAGE ABENDS IN INITIATOR FOR SSI FUNCTIONS

VERIFICATION STEPS:
1) z/OS 2.2 and later, HJE77A0, HJE77B0, HJE77C0
2) Storage abends for jobs in Initiator

155
The ARSRPT function is very useful for taking a look at what is going on within ARSSOCKD.

White Paper here:

https://www.ibm.com/support/pages/arsrpt-%E2%80%93-content-manager-ondemand-enhanced-reporting-utility

Note:  you have to be logging certain messages (mentioned in the White Paper) for ARSRPT to be able report on.


Pro tip:  If ARSRPT says that ODWEK is doing a lot of logon/logoffs, perhaps the ODWEK application is not using connection pooling.

Connection pooling is very much recommended for efficient processing.

Ed

156
z/OS Server / Re: How can ARSYSPIN exploit ARS.PTGN exit ?
« on: April 12, 2021, 08:34:03 AM »
This is just a guess:

Quote
Following is how is defined the ODUSER= and ODUSERPW= in the //ARSPARM:
ARSY0103I <*NOSPINDELAY=     
ARSY0103I < ODHOST=ARCHIVE   
ARSY0103I < ODINSTANCE=ARCHIVE
ARSY0103I < ODUSER=           
ARSY0103I < ODUSERPW=         
ARSY0103I <*OUTCC=       

If in ARSIVPR1 you completely omit the -u and -p, perhaps in ARSPARM you should completely omit the ODUSER and ODUSERPW parms?

Ed

158
z/OS Server / Re: upgrading CMOD z/OS 9.5 to 10.?
« on: March 26, 2021, 02:05:10 PM »
The upgrade steps are in the readme files:

V10.5 README

https://www.ibm.com/support/pages/ibm-content-manager-ondemand-zos-v105-readme

V10.1 README

http://www-01.ibm.com/support/docview.wss?uid=swg27049534

Yes, the upgrade is in USS.

Yes, you can upgrade directly to 10.5.  The 10.5 readme has instructions.

If you upgrade to 10.1 be sure to check out my 10.1 release notes thread here in the z/OS Server section.

If you upgrade directly to 10.5 check out both my 10.1 and 10.5 release notes thread.

What trips up upgrades the most?  Exits not working on a newer release.

Ed Arnold

159
Symptoms seen with the Windows thick client with the 'Microsoft Print to PDF' option include sometimes creating zero length PDFs, sometimes just the graphics and no text, and occasionally leading to the client crashing.

A fix is available, KB5001648.

Ed

160
z/OS Server / Re: 10.1 Release Notes
« on: March 23, 2021, 04:25:24 PM »
Using 31-bit COBOL exits?

New DD def per the ++ACTION HOLD

++HOLD(UI74251) SYSTEM FMID(H272A10) REASON(ACTION) DATE(21062)     
  COMMENT(                                                           
  New DD definition to be added:  ARSSYSOU.     
                   
  Changed DD definition: SYSOUT as used by the CMOD. 
               
  This fix changes the LE runtime options for 31-bit exits.   
     
  Previously, any 31-bit exit COBOL DISPLAYs appeared in SYSOUT.
   
  With this change 31-bit exit COBOL displays will now appear in     
  the ARSSYSOU DD definition.               
                       
  This change fixes a problem with a 64-bit LE enclave interfering   
  with 31-bit LE enclave usage.   
                                   
  It does this by separating 31-bit enclave usage of the MSGFILE     
  with the default of SYSOUT from the 64-bit LE enclave usage of     
  the MSGFILE with the default of SYSOUT.     
                       
  This change will cause any 31-bit exit COBOL DISPLAYs to now       
  appear on a DD of ARSSYSOU instead of a DD of SYSOUT. 
           
  If customers are relying on the output from the exits appearing   
  on the SYSOUT DD, the ARSSYSOU DD needs to be used instead.).
   

161
z/OS Server / Re: CMOD 10.5 Release Notes
« on: March 23, 2021, 04:24:40 PM »
Using 31-bit COBOL exits?

New DD def per the ++ACTION HOLD

++HOLD(UI74252) SYSTEM FMID(H272A50) REASON(ACTION) DATE(21062)     
  COMMENT(                                                           
  New DD definition to be added:  ARSSYSOU.     
                   
  Changed DD definition: SYSOUT as used by the CMOD. 
               
  This fix changes the LE runtime options for 31-bit exits.   
     
  Previously, any 31-bit exit COBOL DISPLAYs appeared in SYSOUT.
   
  With this change 31-bit exit COBOL displays will now appear in     
  the ARSSYSOU DD definition.               
                       
  This change fixes a problem with a 64-bit LE enclave interfering   
  with 31-bit LE enclave usage.   
                                   
  It does this by separating 31-bit enclave usage of the MSGFILE     
  with the default of SYSOUT from the 64-bit LE enclave usage of     
  the MSGFILE with the default of SYSOUT.     
                       
  This change will cause any 31-bit exit COBOL DISPLAYs to now       
  appear on a DD of ARSSYSOU instead of a DD of SYSOUT. 
           
  If customers are relying on the output from the exits appearing   
  on the SYSOUT DD, the ARSSYSOU DD needs to be used instead.).
                                                               

162
z/OS Server / PH31060 may cause an error in ARSUUPDX exit
« on: March 23, 2021, 09:54:53 AM »
PH31060 -                                                           
  ARSUUPDT FIELD ARSCSXITUPDTEXIT-FILENAME VALUE CHANGED IN VERSION 10.1                                                             
  PROBLEM SUMMARY:                                                   
  ****************************************************************   
  * USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1   *   
  *                 and above using arsload -E and loading files *   
  *                 from the JES spool.                          *   
  ****************************************************************   
  * PROBLEM DESCRIPTION: When loading files from the JES spool   *   
  *                      and specifying the -E option to         *   
  *                      arsload, the arsuupdt exit              *   
  *                      ArsCSXitUpdtExit->pFileName parameter   *   
  *                      receives a pointer to a string that     *   
  *                      starts with 'DD:'.  Previously it       *   
  *                      pointed to a string containing a        *   
  *                      psudo-filename like                     *   
  *                      /arsa/tmp/MVS042.BPXAS.ADFOUT.STD.20110 *   
  *                      5.1804170016779814.ARD.                 *   
  ****************************************************************   
  ARGLOAD was inadvertently changed to pass the DD name as the       
  pFileName parameter when processing a spool files.                 
  PROBLEM CONCLUSION:                                               
  ARGLOAD is changed to pass the psudo-filename as the pFileName     
  parameter when processing a spool file. 


Had a report of loads failing.

(a) be sure to test the exit after applying this maintenance

(b) Level 2 might have a workaround

Ed

163
z/OS Server / PH31060 may cause an error in ARSUUPDX exit
« on: March 23, 2021, 09:53:38 AM »
PH31060 -                                                           
  ARSUUPDT FIELD ARSCSXITUPDTEXIT-FILENAME VALUE CHANGED IN VERSION 10.1                                                             
  PROBLEM SUMMARY:                                                   
  ****************************************************************   
  * USERS AFFECTED: All Content Manager OnDemand for z/OS 10.1   *   
  *                 and above using arsload -E and loading files *   
  *                 from the JES spool.                          *   
  ****************************************************************   
  * PROBLEM DESCRIPTION: When loading files from the JES spool   *   
  *                      and specifying the -E option to         *   
  *                      arsload, the arsuupdt exit              *   
  *                      ArsCSXitUpdtExit->pFileName parameter   *   
  *                      receives a pointer to a string that     *   
  *                      starts with 'DD:'.  Previously it       *   
  *                      pointed to a string containing a        *   
  *                      psudo-filename like                     *   
  *                      /arsa/tmp/MVS042.BPXAS.ADFOUT.STD.20110 *   
  *                      5.1804170016779814.ARD.                 *   
  ****************************************************************   
  ARGLOAD was inadvertently changed to pass the DD name as the       
  pFileName parameter when processing a spool files.                 
  PROBLEM CONCLUSION:                                               
  ARGLOAD is changed to pass the psudo-filename as the pFileName     
  parameter when processing a spool file. 


Had a report of loads failing.

(a) be sure to test the exit after applying this maintenance

(b) Level 2 might have a workaround

Ed

164
https://www.ibm.com/support/pages/gui-dsmj-818-aix-client-fails-start-ans1579e-gskkmerrcryptoalgorithm-reported-dsmerror-log

GUI / DSMJ 8.1.8 AIX client fails to start with ANS1579E GSKKM_ERR_CRYPTO_ALGORITHM reported in dsmerror log

Resolving The Problem

This is resolved with fix for Java APAR  IJ17282 .

The fix was shipped in Java 8.0.5.40.

A link in the link above shows how to download the Java fix.

165
MP Server / Re: Issue configuring new environment
« on: March 20, 2021, 12:29:43 PM »

Pages: 1 ... 6 7 8 9 10 [11] 12 13 14 15 16 ... 80