Re: DCBs and DCBEs - Could IBM have done it any worse?

2013-08-22 Thread Klaus Stanislawiak
On Tue, 14 Jun 2011 12:41:11 -0500, Paul Gilmartin wrote:

 I prefer to be told when I make a programming error.

It looks that they are going to tell us soon.
Please see APARs OA42701, OA43000 and OA43037.

--
Klaus Stanislawiak

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: DCBs and DCBEs - Could IBM have done it any worse?

2013-08-22 Thread Paul Gilmartin
On Thu, 22 Aug 2013 01:10:42 -0500, Klaus Stanislawiak wrote:

On Tue, 14 Jun 2011 12:41:11 -0500, Paul Gilmartin wrote:

 I prefer to be told when I make a programming error.

When did I say that?

It looks that they are going to tell us soon.
Please see APARs OA42701, OA43000 and OA43037.
 
Humph!  For OA43037 the Google synopsis says:

Search Results

IBM OA43037: IRRDBU00 MSGIEC190I - United States
www-01.ibm.com/support/docview.wss?crawler=1uid=isg1OA43037‎
Aug 14, 2013 - DFP was enhanced to more closely validate some DCB data.
RACF's Database Unload Utility - IRRDBU00 - was caught using an invalid.

And IBM seems not to want me to view the page:

Our apologies...
The page you requested cannot be displayed
...
Get assistance
This option lets you send an information request and tell us about a broken 
link.
You will receive an e-mail from us to help you find what you need.

Interesting.  I don't think I'll bother to report the broken link.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: DCBs and DCBEs - Could IBM have done it any worse?

2013-08-22 Thread Lizette Koehler
APAR Identifier .. OA42701  Last Changed  13/08/07
  AMATERSE INVOCATION RESULTS IN MSGIEC190I
 
 
  Symptom .. IN INCORROUT Status ... CLOSED  PER
  Severity ... 3  Date Closed . 13/07/26
  Component .. 5752SC112  Duplicate of 
  Reported Release . 790  Fixed Release  999
  Component Name SVA UTILITIESSpecial Notice
  Current Target Date ..13/08/15  Flags
  SCP ...
  Platform 
 
  Status Detail: SHIPMENT - Packaged solution is available for
shipment.
 
  PE PTF List:
 
  PTF List:
  Release 790   : UA70061 available 13/08/07 (1000 )
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  Under certain conditions executing an AMATERSE with the PACK
  option will result in a successful execution, but MSGIEC190I
  xx,STEP,SYSUT3 INVALID DCBE: STORAGE NOT ADDRESSABLE is
  issued.
 
 
  LOCAL FIX:
 
 
  PROBLEM SUMMARY:
  
  * USERS AFFECTED: All users of AMATERSE on release HBB7790.*
  
  * PROBLEM DESCRIPTION: AMATERSE MSGIEC190I INVALID DCBE:   *
  *  STORAGE NOT ADDRESSABLE *
  
  * RECOMMENDATION:  *
  
  While PACK/ UNPACKing a PDS data set, AMATERSE may successfully
  complete, but MSGIEC190I is issued. Also, AMATERSE fails to use
  system determined blocksize for PACK/SPACK output.
 
 
  PROBLEM CONCLUSION:
  AMATERSE's PACK and UNPACK processing is updated to correctly
  set the relevant DCB data, to prevent the IEC190I message. Also,
  AMATERSE's processing is changed to allow System Determined
  Blocksize for the PACK/SPACK output data set.
 


Lizette

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Thursday, August 22, 2013 4:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DCBs and DCBEs - Could IBM have done it any worse?

On Thu, 22 Aug 2013 01:10:42 -0500, Klaus Stanislawiak wrote:

On Tue, 14 Jun 2011 12:41:11 -0500, Paul Gilmartin wrote:

 I prefer to be told when I make a programming error.

When did I say that?

It looks that they are going to tell us soon.
Please see APARs OA42701, OA43000 and OA43037.
 
Humph!  For OA43037 the Google synopsis says:

Search Results

IBM OA43037: IRRDBU00 MSGIEC190I - United States
www-01.ibm.com/support/docview.wss?crawler=1uid=isg1OA43037‎
Aug 14, 2013 - DFP was enhanced to more closely validate some DCB data.
RACF's Database Unload Utility - IRRDBU00 - was caught using an invalid.

And IBM seems not to want me to view the page:

Our apologies...
The page you requested cannot be displayed
...
Get assistance
This option lets you send an information request and tell us about a broken 
link.
You will receive an e-mail from us to help you find what you need.

Interesting.  I don't think I'll bother to report the broken link.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: DCBs and DCBEs - Could IBM have done it any worse?

2013-08-22 Thread John P Kalinich
These 2 APARS also address the IEC190I issue.

1.  APAR OA42406: OCE FIX ROLLUP FOR HDZ2210: Individual APAR status

A fix is available.  The life cycle of this APAR is complete.
http://www-01.ibm.com/support/docview.wss?uid=isg1OA42406myns=aparmynp
=DOCTYPEstatusmync=E


2.  APAR OA42694: ABEND0C4 IFG0554P: Individual APAR status

A fix is available.  The life cycle of this APAR is complete.
http://www-01.ibm.com/support/docview.wss?uid=isg1OA42694myns=aparmynp
=DOCTYPEstatusmync=E

Regards,
John K

Lizette K of the IBM Mainframe Discussion List IBM-MAIN@listserv.ua.edu
wrote on 08/22/2013 07:22:11 AM:

 APAR Identifier .. OA42701  Last Changed  13/08/07
   AMATERSE INVOCATION RESULTS IN MSGIEC190I


   Symptom .. IN INCORROUT Status ... CLOSED  PER
   Severity ... 3  Date Closed . 13/07/26
   Component .. 5752SC112  Duplicate of 
   Reported Release . 790  Fixed Release  999
   Component Name SVA UTILITIESSpecial Notice
   Current Target Date ..13/08/15  Flags
   SCP ...
   Platform 

   Status Detail: SHIPMENT - Packaged solution is available for
 shipment.

   PE PTF List:

   PTF List:
   Release 790   : UA70061 available 13/08/07 (1000 )


   Parent APAR:
   Child APAR list:


   ERROR DESCRIPTION:
   Under certain conditions executing an AMATERSE with the PACK
   option will result in a successful execution, but MSGIEC190I
   xx,STEP,SYSUT3 INVALID DCBE: STORAGE NOT ADDRESSABLE is
   issued.


   LOCAL FIX:


   PROBLEM SUMMARY:
   
   * USERS AFFECTED: All users of AMATERSE on release HBB7790.*
   
   * PROBLEM DESCRIPTION: AMATERSE MSGIEC190I INVALID DCBE:   *
   *  STORAGE NOT ADDRESSABLE *
   
   * RECOMMENDATION:  *
   
   While PACK/ UNPACKing a PDS data set, AMATERSE may successfully
   complete, but MSGIEC190I is issued. Also, AMATERSE fails to use
   system determined blocksize for PACK/SPACK output.


   PROBLEM CONCLUSION:
   AMATERSE's PACK and UNPACK processing is updated to correctly
   set the relevant DCB data, to prevent the IEC190I message. Also,
   AMATERSE's processing is changed to allow System Determined
   Blocksize for the PACK/SPACK output data set.



 Lizette

 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU
 ] On Behalf Of Paul Gilmartin
 Sent: Thursday, August 22, 2013 4:21 AM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: DCBs and DCBEs - Could IBM have done it any worse?

 On Thu, 22 Aug 2013 01:10:42 -0500, Klaus Stanislawiak wrote:

 On Tue, 14 Jun 2011 12:41:11 -0500, Paul Gilmartin wrote:
 
  I prefer to be told when I make a programming error.
 
 When did I say that?

 It looks that they are going to tell us soon.
 Please see APARs OA42701, OA43000 and OA43037.
 
 Humph!  For OA43037 the Google synopsis says:

 Search Results

 IBM OA43037: IRRDBU00 MSGIEC190I - United States
 www-01.ibm.com/support/docview.wss?crawler=1uid=isg1OA43037‎
 Aug 14, 2013 - DFP was enhanced to more closely validate some DCB
data.
 RACF's Database Unload Utility - IRRDBU00 - was caught using an
invalid.

 And IBM seems not to want me to view the page:

 Our apologies...
 The page you requested cannot be displayed
 ...
 Get assistance
 This option lets you send an information request and tell us
 about a broken link.
 You will receive an e-mail from us to help you find what you need.

 Interesting.  I don't think I'll bother to report the broken link.

 -- gil

 --
 For IBM-MAIN subscribe / signoff / archive access instructions, send
 email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

 --
 For IBM-MAIN subscribe / signoff / archive access instructions,
 send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: DCBs and DCBEs - Could IBM have done it any worse?

2013-08-22 Thread Lizette Koehler
Here is  OA43037


https://www-304.ibm.com/ibmlink/sis/viewAparDoc.wss?context=aparAndUsagedocumentIds=OA43037searchWords=OA43037libraryType=Dlc=encc=US

http://tinyurl.com/mw3uht3



  APAR Identifier .. OA43037  Last Changed  13/08/21
  IRRDBU00 MSGIEC190I
 
 
  Symptom .. MS MSGIEC190IStatus ... OPEN
  Severity ... 3  Date Closed .
  Component .. 5752XXH00  Duplicate of 
  Reported Release . 790  Fixed Release 
  Component Name RACF Special Notice
  Current Target Date ..13/10/31  Flags
  SCP ...
  Platform 
 
  Status Detail: REVIEW - APAR solution is being reviewed.
 
  PE PTF List:
 
  PTF List:
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  DFP was enhanced to more closely validate some DCB data.  RACF's
  Database Unload Utility - IRRDBU00 - was not correctly
  initialzing the DCBE.  This caused msg IEC190I to be issued:
   IEC190I TECH008R,UNLOAD,INDD1 INVALID DCBE: DCBHIARC FLAGS ON
   BUT NO DCBE PTR
 
  msgIEC190 IEC190
 
 
  LOCAL FIX:
  None, but IRRDBU00 still works, so just ignore the msgs.


Here is OA43000

APAR Identifier .. OA43000  Last Changed  13/08/08
  IEC190I DURING RECALL OF PDSE DATA SET
 
 
  Symptom .. IN INCORROUT Status ... CLOSED  PER
  Severity ... 3  Date Closed . 13/08/08
  Component .. 5695DF175  Duplicate of 
  Reported Release . 210  Fixed Release  999
  Component Name DFSMSDSS, ISMF   Special Notice
  Current Target Date ..  Flags
  SCP ...
  Platform 
 
  Status Detail: TESTPACKAGING - Packaged solution is being tested.
 
  PE PTF List:
 
  PTF List:
  Release 210   : PTF not available yet
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  During DFSMShsm Recall of a PDSE message IEC190, Invalid DCBE is
  issued.
 
 
  LOCAL FIX:
  NONE
 
 
  PROBLEM SUMMARY:
  
  * USERS AFFECTED: Users of DFSMSdss processing PDSEs using *
  * either logical data set RESTORE or DFSMShsm  *
  * RECALL   *
  
  * PROBLEM DESCRIPTION: IEC190I is received when performing *
  *  a DFSMShsm recall of a PDSE.  The   *
  *  IEC190I indicates an invalid DCBE:  *
  *  storage not addressable *
  
  * RECOMMENDATION:  *
  
 
 
 
  PROBLEM CONCLUSION:
  DFSMSdss has been modified to pass a valid DCBE when opening
  a PDSE.

Lizette

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Lizette Koehler
Sent: Thursday, August 22, 2013 5:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: DCBs and DCBEs - Could IBM have done it any worse?

APAR Identifier .. OA42701  Last Changed  13/08/07
  AMATERSE INVOCATION RESULTS IN MSGIEC190I
 
 
  Symptom .. IN INCORROUT Status ... CLOSED  PER
  Severity ... 3  Date Closed . 13/07/26
  Component .. 5752SC112  Duplicate of 
  Reported Release . 790  Fixed Release  999
  Component Name SVA UTILITIESSpecial Notice
  Current Target Date ..13/08/15  Flags
  SCP ...
  Platform 
 
  Status Detail: SHIPMENT - Packaged solution is available for
shipment.
 
  PE PTF List:
 
  PTF List:
  Release 790   : UA70061 available 13/08/07 (1000 )
 
 
  Parent APAR:
  Child APAR list:
 
 
  ERROR DESCRIPTION:
  Under certain conditions executing an AMATERSE with the PACK
  option will result in a successful execution, but MSGIEC190I
  xx,STEP,SYSUT3 INVALID DCBE: STORAGE NOT ADDRESSABLE is
  issued.
 
 
  LOCAL FIX:
 
 
  PROBLEM SUMMARY:
  
  * USERS AFFECTED: All users of AMATERSE on release HBB7790.*
  
  * PROBLEM DESCRIPTION: AMATERSE MSGIEC190I INVALID DCBE:   *
  *  STORAGE NOT ADDRESSABLE *
  
  * RECOMMENDATION:  *
  
  While PACK/ UNPACKing a PDS data set, AMATERSE may successfully
  complete, but MSGIEC190I is issued. Also, AMATERSE fails to use
  system determined blocksize for PACK/SPACK output