Re: JES2 Mods

2016-11-10 Thread Lizette Koehler
It will help to know specifically what the issue is.

/*ROUTE XEQ 
/*JOBPARM S=

If so, what are the issues, or error messages you get?

Or is it something else?

This might be something that IBM Support could be more helpful with - as you 
might need assistance in coded JES2 Exits.

Depending on the level of OS for MVS you are running, a lot of the functions in 
the older JES2 Mods is now incorporated into JES2.  If you could provide 
specific information the List can be very helpful.


After a little searching on the WEB is JTIP this function:
the JES2/TSO Interface Package which was used by Mutual Life of Canada, General 
Electric and even the IBM Development Labs. This has now been replaced by SDSF.


Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Elaine Beal
> Sent: Thursday, November 10, 2016 8:56 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JES2 Mods
> 
> I'm working with Larry. We tried removing the JTIP mods but basically gave up.
> There are a lot of old mods on our system and we had to keep backing them off
> and could never get JES working.
> We actually got the maintenance (RSU1501) applied and the only thing that
> doesn't work is SYSAFF Any thoughts?
> 
> Thanks,
> Elaine

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


Re: SUPRESSING MESSAGES - DFHSM

2016-11-10 Thread esmie moo
Lizette,

Thanks for the suggestion.  I was in the process of searching the REDBOOKS when 
it was suggested to use the ACTLOGMSGLVL(EXCEPTIONONLY)

Thanks to all who helped me out.

On Tue, 11/8/16, Lizette Koehler  wrote:

 Subject: Re: SUPRESSING MESSAGES - DFHSM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Tuesday, November 8, 2016, 9:28 AM
 
 So did you search
 www.ibm.com?
 
 I went there
 and used in the search box
 
 suppress dfhsm activity log message
 
 Came up with a hit that
 probably meets your need.
 
 Try this.  If you cannot find the link, let me
 know
 
 Controlling the amount
 of information written to the activity logs
 
 The activity logs can provide
 a large amount of information, making it time-consuming to
 examine each log. You can reduce the time that is required
 to examine the logs in two ways: by controlling the amount
 of information written to the logs and by providing for
 online analysis of the logs.
 
 
 
 Lizette
 
 
 > -Original
 Message-
 > From: IBM Mainframe
 Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On
 > Behalf Of esmie moo
 > Sent: Tuesday, November 08, 2016 5:12
 AM
 > To: IBM-MAIN@LISTSERV.UA.EDU
 > Subject: Re: SUPRESSING MESSAGES -
 DFHSM
 > 
 > Sorry I
 should have stated my question more clearly.  In the HSM
 Activity log
 > several messages ARC0734I
 ACTION=SPCMGMT are being logged and I don't want
 > them displayed in the Activity log.  I
 remember modifying the parm in ARCCMD90
 >
 to supress these messages.
 > 
 >
 
 > On Mon, 11/7/16, Lizette Koehler 
 wrote:
 > 
 >  Subject:
 Re: SUPRESSING MESSAGES - DFHSM
 >  To:
 IBM-MAIN@LISTSERV.UA.EDU
 >  Received: Monday, November 7, 2016,
 12:28 PM
 > 
 >  So
 what do you want to
 >  suppress?
 > 
 >  Is this from
 >  DFHSM producing the message at all?
 > 
 >  Using the MPF list
 to suppress the message?
 > 
 >  Using a tool like CA OPS/MVS
 >  or IBM Tivoli to suppress the
 message?
 > 
 >  I am
 not sure what solution you are looking  for.
 > 
 >  Did you try
 searching
 >  in www.ibm.com for how to
 do this?
 > 
 > 
 >  If you think the messages are
 >  too frequent, then maybe you should open
 an SR to IBM to see  why that is
 >
 occurring?  Perhaps you have something running  too
 often.
 > 
 > 
 Lizette
 > 
 > 
 >  > -Original
 >  Message-
 >  >
 From: IBM Mainframe
 >  Discussion List
 [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
 On  > Behalf Of esmie moo
 > >
 Sent: Monday, November 07, 2016 9:50 AM  > To: IBM-MAIN@LISTSERV.UA.EDU 
 >
 > Subject: SUPRESSING MESSAGES -
 DFHSM  >  > Gentle Readers,  >  > One of
 our
 > HSM  STC's has been inundated
 with ARC0734I ACTION=SPCMGMT.  I  > remember
 > that there is a SETSYS parm  in the HSM
 parmlib which would allow us  >  to
 > supress these messages.  I cannot
 remember the parm  name.  Can anybody  >
 > suggest what it  is?
 >  >
 >  > Thanks
 In
 >  advance.
 > 
 >
 
 --
 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: SUPRESSING MESSAGES - DFHSM

2016-11-10 Thread esmie moo
Thanks Anthony.  It worked.  I couldn't remember the parm.  Thanks

On Tue, 11/8/16, Anthony Thompson  wrote:

 Subject: Re: SUPRESSING MESSAGES - DFHSM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Received: Tuesday, November 8, 2016, 7:35 PM
 
 What about:
 
 SETSYS
 ACTLOGMSGLVL(EXCEPTIONONLY)
 
 Ant.
 
 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of esmie moo
 Sent: Tuesday, 8
 November 2016 9:42 PM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: SUPRESSING MESSAGES - DFHSM
 
 Sorry I should have stated my
 question more clearly.  In the HSM Activity log several
 messages ARC0734I ACTION=SPCMGMT are being logged and I
 don't want them displayed in the Activity log.  I
 remember modifying the parm in ARCCMD90 to supress these
 messages.
   
 
 On Mon, 11/7/16, Lizette Koehler 
 wrote:
 
  Subject: Re:
 SUPRESSING MESSAGES - DFHSM
  To: IBM-MAIN@LISTSERV.UA.EDU
  Received: Monday, November 7, 2016, 12:28
 PM
  
  So what do you want
 to
  suppress?
  
  Is this from
  DFHSM producing
 the message at all?
  
  Using
 the MPF list to suppress the message?
  
  Using a tool like CA OPS/MVS
 
 or IBM Tivoli to suppress the message?
  
  I am not sure what solution you are looking 
 for.
  
  Did you try
 searching
  in www.ibm.com for how to do
 this?
  
  
 
 If you think the messages are
  too frequent,
 then maybe you should open an SR to IBM to see  why that is
 occurring?  Perhaps you have something running  too
 often.
  
  Lizette
  
  
  >
 -Original
  Message-
 
 > From: IBM Mainframe
  Discussion List
 [mailto:IBM-MAIN@LISTSERV.UA.EDU] 
 On  > Behalf Of esmie moo  > Sent: Monday, November
 07, 2016 9:50 AM  > To: IBM-MAIN@LISTSERV.UA.EDU 
 > Subject: SUPRESSING MESSAGES - DFHSM  >  >
 Gentle Readers,  >  > One of our HSM  STC's has
 been inundated with ARC0734I ACTION=SPCMGMT.  I  >
 remember that there is a SETSYS parm  in the HSM parmlib
 which would allow us  >  to supress these messages.  I
 cannot remember the parm  name.  Can anybody  >
 suggest what it  is?
  >
 
 > Thanks In
  advance.
 
 > 
  
 
 --
  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
 

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


Re: JES2 Mods

2016-11-10 Thread John Eells
When you say "SYSAFF doesn't work," exactly what is it that happens?  Is 
SYSAFF ignored?  Are there error messages issued?  Can you post the JOB 
and JECL statements and the messages you get?


Elaine Beal wrote:

I'm working with Larry. We tried removing the JTIP mods but basically gave up. 
There are a lot of old mods on our system and we had to keep backing them off 
and could never get JES working.
We actually got the maintenance (RSU1501) applied and the only thing that 
doesn't work is SYSAFF
Any thoughts?


--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com

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


Re: JES2 Mods

2016-11-10 Thread Allan Staller
Thruput Manager?  OSEM?   WLM SCHEDULING ENVIRONMENTS?



-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Elaine Beal
Sent: Thursday, November 10, 2016 9:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: JES2 Mods

I'm working with Larry. We tried removing the JTIP mods but basically gave up. 
There are a lot of old mods on our system and we had to keep backing them off 
and could never get JES working.
We actually got the maintenance (RSU1501) applied and the only thing that 
doesn't work is SYSAFF Any thoughts?

Thanks,
Elaine

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


::DISCLAIMER::


The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.




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


Re: JES2 Mods

2016-11-10 Thread Elaine Beal
I'm working with Larry. We tried removing the JTIP mods but basically gave up. 
There are a lot of old mods on our system and we had to keep backing them off 
and could never get JES working.
We actually got the maintenance (RSU1501) applied and the only thing that 
doesn't work is SYSAFF
Any thoughts?

Thanks,
Elaine

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


Reddit AMA on z/OS and the API Economy TODAY

2016-11-10 Thread Anthony Giorgio

Hey everyone!

We will be hosting a Reddit AMA TODAY at 11AM ET!  Join Frank De Gilio 
and Charlie Lawrence to discuss IBM z/OS and the API Economy.


https://redd.it/595d6l

--
Anthony Giorgio
Advisory Software Engineer
IBM z Systems Hypervisor Performance Manager
Twitter: @a_giorgio

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


Re: Problem with startup DB2

2016-11-10 Thread Jim Mulder
  A 028-04000200 would not be due to either of those things.  A more 
likely cause
would be a page table overlay.   The first step for doing any diagnosis 
would be 
 
SLIP MOD,ID=X028,DISABLE

and then reproduce the problem.   Open a PMR and send the dump to IBM.

Jim Mulder z/OS Diagnosis, Design, Development, Test  IBM Corp. 
Poughkeepsie NY


> Have you looked this up?
> 
> DB9GDBM1 DB9GDBM1 - ABEND=S028 U REASON=04000200
> 
> ABEND028 is a failure in the paging subsystem. The reason code is 
> not documented in the manual IBM could give you more information.
> 
> 2 things you can quickly check. 1) is the MVS region size 
> sufficient?  2) Do you have an adequate paging subsystem?



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


Re: EXTERNAL: wget for omvs?

2016-11-10 Thread Rick Troth

Mumble fumble sometime last month Jerry said:



>Curl would be what I would use on zOS to do the same function as wget -
> (Ithink it can use wget under the covers)


To which Mark replied:

I don't believe that to be true.
One feature that wget has that curl does not is recursively downloading entire 
trees,
while maintaining last-modified dates, etc.  If you're only downloading one file
here and there, and don't mind the dates not matching, then curl is just fine.
Doing more than that is certainly possible (it's a very powerful command
in a lot of ways), but you'll start getting into scripting things.


indeed
CURL and WGET are independent projects. They share some capabilities but 
they're not the same thing.


For any who might be interested, there are CURL and WGET for CMS (subset 
implementations) which could be made to work on TSO.


-- R; <><






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


Re: Problem with startup DB2

2016-11-10 Thread Allan Staller
The DB mount failure is probably a secondary effect of the Abend028.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Allan Staller
Sent: Thursday, November 10, 2016 7:33 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Problem with startup DB2

Have you looked this up?

DB9GDBM1 DB9GDBM1 - ABEND=S028 U REASON=04000200

ABEND028 is a failure in the paging subsystem. The reason code is not 
documented in the manual IBM could give you more information.

2 things you can quickly check. 1) is the MVS region size sufficient?  2) Do 
you have an adequate paging subsystem?

HTH,

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Hilario Garcia
Sent: Thursday, November 10, 2016 4:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Problem with startup DB2

Hello,

After a hard stop of the partition, DB2 does not start and produces the 
following messages;

  -DB9G START DB2
  S DB9GMSTR
  $HASP100 DB9GMSTR ON STCINRDR
  IEF695I START DB9GMSTR WITH JOBNAME DB9GMSTR IS ASSIGNED TO USER START2
   , GROUP SYS1
  $HASP373 DB9GMSTR STARTED
  IEF403I DB9GMSTR - STARTED - TIME=13.51.31
  DSNY024I  -DB9G DSNYASCP MSTR INITIALIZATION IS STARTING
  DSNZ002I -DB9G DSNZINIT SUBSYSTEM DB9G SYSTEM PARAMETERS LOAD MODULE
  NAME IS DB9GPARM
  DSNZ016I  -DB9G DSNZINIT 093
  SUBSYSTEM DB9G SYSTEM PARAMETERS ARE AS FOLLOWS:
SYSTEM PARM  DSN910.DB9G.SDSNEXIT(DB9GPARM)
DSNHDECP DSN910.DB9G.SDSNEXIT(DSNHDECP)
ACCESS EXIT  DSN910.DB9G.SDSNEXIT(DSNX@XAC)
IDAUTH EXIT  DSN910.DB9G.SDSNEXIT(DSN3@ATH)
SIGNON EXIT  DSN910.DB9G.SDSNEXIT(DSN3@SGN)
  DSN7407I  -DB9G DSN7GAR1 094
  AUTOMATIC RESTART MANAGER REGISTER FAILED.
MVS IXCARM RETURN CODE = 000C,
MVS IXCARM REASON CODE = 0160.
  S DB9GIRLM
  $HASP100 DB9GIRLM ON STCINRDR
  IEF695I START DB9GIRLM WITH JOBNAME DB9GIRLM IS ASSIGNED TO USER START2
   , GROUP SYS1
  $HASP373 DB9GIRLM STARTED
  IEF403I DB9GIRLM - STARTED - TIME=13.51.39
  DXR180I DJ9G001 AUTOMATIC RESTART MANAGER IS NOT ENABLED
  DXR117I DJ9G001 INITIALIZATION COMPLETE
  DSNY001I  -DB9G SUBSYSTEM STARTING
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 103
  IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 104
  IEC161I DSN910.DB9G.BSDS01.INDEX,USERCAT.Z110.DB2V9
  IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 105
  IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 106
  IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 107
  IEC161I DSN910.DB9G.BSDS02.INDEX,USERCAT.Z110.DB2V9
  IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 108
  IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
  DSNJ127I  -DB9G SYSTEM TIMESTAMP FOR BSDS= 16.295 08:27:14.61
  DSNJ001I  -DB9G DSNJW007 CURRENT COPY 1 ACTIVE LOG 110
  DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY1.DS02,
  STARTRBA=00015180,ENDRBA=0001539B
  DSNJ001I  -DB9G DSNJW007 CURRENT COPY 2 ACTIVE LOG 111
  DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY2.DS02,
  STARTRBA=00015180,ENDRBA=0001539B
  DSNJ099I  -DB9G LOG RECORDING TO COMMENCE WITH 112
  STARTRBA=000152F2D000
  S DB9GDBM1
  $HASP100 DB9GDBM1 ON STCINRDR
SYSTEM ID SYS1 DATE 10/28/2016 2016.302 LINE   6,664  PAGE   2
  IEF695I START DB9GDBM1 WITH JOBNAME DB9GDBM1 IS ASSIGNED TO USER START2
   , GROUP SYS1
  $HASP373 DB9GDBM1 STARTED
  IEF403I DB9GDBM1 - STARTED - TIME=13.51.52
  DSNY024I  -DB9G DSNYASCP DBM1 INITIALIZATION IS STARTING
  IEA989I SLIP TRAP ID=X028 MATCHED.  JOBNAME=DB9GDBM1, ASID=0041.
 *DSNV086E -DB9G DB2 ABNORMAL TERMINATION REASON=00E80100
  IEA989I SLIP TRAP ID=X47B MATCHED.  JOBNAME=DB9GMSTR, ASID=0040.
  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DB9GMSTR, ASID=0040.
  IEF450I DB9GDBM1 DB9GDBM1 - ABEND=S028 U REASON=04000200 175
  TIME=13.51.59
  IEF404I DB9GDBM1 - ENDED - TIME=13.51.59
  $HASP395 DB9GDBM1 ENDED
  DXR110I DJ9G001 STOP COMMAND ACCEPTED
  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=0041.
  IEF450I DB9GMSTR DB9GMSTR - ABEND=S04F U REASON= 180
  TIME=13.51.59
  $HASP250 DB9GDBM1 PURGED -- (JOB KEY WAS D18FC9B3)
  DXR121I DJ9G001 END-OF-TASK CLEANUP SUCCESSFUL - HI-CSA377K  -
  HI-ACCT-CSA  0K
  IEF404I DB9GMSTR - ENDED - TIME=13.52.00
  $HASP395 DB9GMSTR ENDED
  IEF404I DB9GIRLM - ENDED - TIME=13.52.00
  IEF352I ADDRESS SPACE UNAVAILABLE
  $HASP395 DB9GIRLM ENDED
  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=0040.
  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=003D.
  $HASP250 DB9GIRLM PURGED -- (JOB KEY WAS D18FC9A7)
  $HASP250 DB9GMSTR PURGED -- (JOB KEY WAS D18FC99F)
  DSN3104I -DB9G DSN3EC0X - TERMINATION COMPLETE
  DSN3100I -DB9G DSN3EC0X - SUBSYSTEM DB9G READY FOR START COMMAND 

I have also looked at the 

Re: Problem with startup DB2

2016-11-10 Thread Allan Staller
Have you looked this up?

DB9GDBM1 DB9GDBM1 - ABEND=S028 U REASON=04000200

ABEND028 is a failure in the paging subsystem. The reason code is not 
documented in the manual IBM could give you more information.

2 things you can quickly check. 1) is the MVS region size sufficient?  2) Do 
you have an adequate paging subsystem?

HTH,

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Hilario Garcia
Sent: Thursday, November 10, 2016 4:53 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Problem with startup DB2

Hello,

After a hard stop of the partition, DB2 does not start and produces the 
following messages;

  -DB9G START DB2
  S DB9GMSTR
  $HASP100 DB9GMSTR ON STCINRDR
  IEF695I START DB9GMSTR WITH JOBNAME DB9GMSTR IS ASSIGNED TO USER START2
   , GROUP SYS1
  $HASP373 DB9GMSTR STARTED
  IEF403I DB9GMSTR - STARTED - TIME=13.51.31
  DSNY024I  -DB9G DSNYASCP MSTR INITIALIZATION IS STARTING
  DSNZ002I -DB9G DSNZINIT SUBSYSTEM DB9G SYSTEM PARAMETERS LOAD MODULE
  NAME IS DB9GPARM
  DSNZ016I  -DB9G DSNZINIT 093
  SUBSYSTEM DB9G SYSTEM PARAMETERS ARE AS FOLLOWS:
SYSTEM PARM  DSN910.DB9G.SDSNEXIT(DB9GPARM)
DSNHDECP DSN910.DB9G.SDSNEXIT(DSNHDECP)
ACCESS EXIT  DSN910.DB9G.SDSNEXIT(DSNX@XAC)
IDAUTH EXIT  DSN910.DB9G.SDSNEXIT(DSN3@ATH)
SIGNON EXIT  DSN910.DB9G.SDSNEXIT(DSN3@SGN)
  DSN7407I  -DB9G DSN7GAR1 094
  AUTOMATIC RESTART MANAGER REGISTER FAILED.
MVS IXCARM RETURN CODE = 000C,
MVS IXCARM REASON CODE = 0160.
  S DB9GIRLM
  $HASP100 DB9GIRLM ON STCINRDR
  IEF695I START DB9GIRLM WITH JOBNAME DB9GIRLM IS ASSIGNED TO USER START2
   , GROUP SYS1
  $HASP373 DB9GIRLM STARTED
  IEF403I DB9GIRLM - STARTED - TIME=13.51.39
  DXR180I DJ9G001 AUTOMATIC RESTART MANAGER IS NOT ENABLED
  DXR117I DJ9G001 INITIALIZATION COMPLETE
  DSNY001I  -DB9G SUBSYSTEM STARTING
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 103
  IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 104
  IEC161I DSN910.DB9G.BSDS01.INDEX,USERCAT.Z110.DB2V9
  IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 105
  IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 106
  IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 107
  IEC161I DSN910.DB9G.BSDS02.INDEX,USERCAT.Z110.DB2V9
  IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 108
  IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
  DSNJ127I  -DB9G SYSTEM TIMESTAMP FOR BSDS= 16.295 08:27:14.61
  DSNJ001I  -DB9G DSNJW007 CURRENT COPY 1 ACTIVE LOG 110
  DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY1.DS02,
  STARTRBA=00015180,ENDRBA=0001539B
  DSNJ001I  -DB9G DSNJW007 CURRENT COPY 2 ACTIVE LOG 111
  DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY2.DS02,
  STARTRBA=00015180,ENDRBA=0001539B
  DSNJ099I  -DB9G LOG RECORDING TO COMMENCE WITH 112
  STARTRBA=000152F2D000
  S DB9GDBM1
  $HASP100 DB9GDBM1 ON STCINRDR
SYSTEM ID SYS1 DATE 10/28/2016 2016.302 LINE   6,664  PAGE   2
  IEF695I START DB9GDBM1 WITH JOBNAME DB9GDBM1 IS ASSIGNED TO USER START2
   , GROUP SYS1
  $HASP373 DB9GDBM1 STARTED
  IEF403I DB9GDBM1 - STARTED - TIME=13.51.52
  DSNY024I  -DB9G DSNYASCP DBM1 INITIALIZATION IS STARTING
  IEA989I SLIP TRAP ID=X028 MATCHED.  JOBNAME=DB9GDBM1, ASID=0041.
 *DSNV086E -DB9G DB2 ABNORMAL TERMINATION REASON=00E80100
  IEA989I SLIP TRAP ID=X47B MATCHED.  JOBNAME=DB9GMSTR, ASID=0040.
  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DB9GMSTR, ASID=0040.
  IEF450I DB9GDBM1 DB9GDBM1 - ABEND=S028 U REASON=04000200 175
  TIME=13.51.59
  IEF404I DB9GDBM1 - ENDED - TIME=13.51.59
  $HASP395 DB9GDBM1 ENDED
  DXR110I DJ9G001 STOP COMMAND ACCEPTED
  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=0041.
  IEF450I DB9GMSTR DB9GMSTR - ABEND=S04F U REASON= 180
  TIME=13.51.59
  $HASP250 DB9GDBM1 PURGED -- (JOB KEY WAS D18FC9B3)
  DXR121I DJ9G001 END-OF-TASK CLEANUP SUCCESSFUL - HI-CSA377K  -
  HI-ACCT-CSA  0K
  IEF404I DB9GMSTR - ENDED - TIME=13.52.00
  $HASP395 DB9GMSTR ENDED
  IEF404I DB9GIRLM - ENDED - TIME=13.52.00
  IEF352I ADDRESS SPACE UNAVAILABLE
  $HASP395 DB9GIRLM ENDED
  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=0040.
  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=003D.
  $HASP250 DB9GIRLM PURGED -- (JOB KEY WAS D18FC9A7)
  $HASP250 DB9GMSTR PURGED -- (JOB KEY WAS D18FC99F)
  DSN3104I -DB9G DSN3EC0X - TERMINATION COMPLETE
  DSN3100I -DB9G DSN3EC0X - SUBSYSTEM DB9G READY FOR START COMMAND 

I have also looked at the System Log and the following error messages appear:

IOEZ1E zFS I / O error 2101520 occurred for aggregate DSN910.SDSNAZF 
IOEZ2E MMRE error id = 31 cis = 11 if = 0 of = 15 buf = 7E4A4000 CI = 0 
BPXF002I FILE SYSTEM DSN910.SDSNAZFS WAS 984 NOT MOUNTED. RETURN CODE = 
008A, REASON CODE = 

Re: Problem with startup DB2

2016-11-10 Thread Lizette Koehler
Probably best to open an SR with IBM.  They will be able to work with you on 
this issue and provide excellent guidance on how to resolve this issue.

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Hilario Garcia
> Sent: Thursday, November 10, 2016 3:53 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Problem with startup DB2
> 
> Hello,
> 
> After a hard stop of the partition, DB2 does not start and produces the
> following messages;
> 
>   -DB9G START DB2
>   S DB9GMSTR
>   $HASP100 DB9GMSTR ON STCINRDR
>   IEF695I START DB9GMSTR WITH JOBNAME DB9GMSTR IS ASSIGNED TO USER START2
>, GROUP SYS1
>   $HASP373 DB9GMSTR STARTED
>   IEF403I DB9GMSTR - STARTED - TIME=13.51.31
>   DSNY024I  -DB9G DSNYASCP MSTR INITIALIZATION IS STARTING
>   DSNZ002I -DB9G DSNZINIT SUBSYSTEM DB9G SYSTEM PARAMETERS LOAD MODULE
>   NAME IS DB9GPARM
>   DSNZ016I  -DB9G DSNZINIT 093
>   SUBSYSTEM DB9G SYSTEM PARAMETERS ARE AS FOLLOWS:
> SYSTEM PARM  DSN910.DB9G.SDSNEXIT(DB9GPARM)
> DSNHDECP DSN910.DB9G.SDSNEXIT(DSNHDECP)
> ACCESS EXIT  DSN910.DB9G.SDSNEXIT(DSNX@XAC)
> IDAUTH EXIT  DSN910.DB9G.SDSNEXIT(DSN3@ATH)
> SIGNON EXIT  DSN910.DB9G.SDSNEXIT(DSN3@SGN)
>   DSN7407I  -DB9G DSN7GAR1 094
>   AUTOMATIC RESTART MANAGER REGISTER FAILED.
> MVS IXCARM RETURN CODE = 000C,
> MVS IXCARM REASON CODE = 0160.
>   S DB9GIRLM
>   $HASP100 DB9GIRLM ON STCINRDR
>   IEF695I START DB9GIRLM WITH JOBNAME DB9GIRLM IS ASSIGNED TO USER START2
>, GROUP SYS1
>   $HASP373 DB9GIRLM STARTED
>   IEF403I DB9GIRLM - STARTED - TIME=13.51.39
>   DXR180I DJ9G001 AUTOMATIC RESTART MANAGER IS NOT ENABLED
>   DXR117I DJ9G001 INITIALIZATION COMPLETE
>   DSNY001I  -DB9G SUBSYSTEM STARTING
>   IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 103
>   IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
>   IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 104
>   IEC161I DSN910.DB9G.BSDS01.INDEX,USERCAT.Z110.DB2V9
>   IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 105
>   IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
>   IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 106
>   IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
>   IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 107
>   IEC161I DSN910.DB9G.BSDS02.INDEX,USERCAT.Z110.DB2V9
>   IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 108
>   IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
>   DSNJ127I  -DB9G SYSTEM TIMESTAMP FOR BSDS= 16.295 08:27:14.61
>   DSNJ001I  -DB9G DSNJW007 CURRENT COPY 1 ACTIVE LOG 110
>   DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY1.DS02,
>   STARTRBA=00015180,ENDRBA=0001539B
>   DSNJ001I  -DB9G DSNJW007 CURRENT COPY 2 ACTIVE LOG 111
>   DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY2.DS02,
>   STARTRBA=00015180,ENDRBA=0001539B
>   DSNJ099I  -DB9G LOG RECORDING TO COMMENCE WITH 112
>   STARTRBA=000152F2D000
>   S DB9GDBM1
>   $HASP100 DB9GDBM1 ON STCINRDR
> SYSTEM ID SYS1 DATE 10/28/2016 2016.302 LINE   6,664  PAGE   2
>   IEF695I START DB9GDBM1 WITH JOBNAME DB9GDBM1 IS ASSIGNED TO USER START2
>, GROUP SYS1
>   $HASP373 DB9GDBM1 STARTED
>   IEF403I DB9GDBM1 - STARTED - TIME=13.51.52
>   DSNY024I  -DB9G DSNYASCP DBM1 INITIALIZATION IS STARTING
>   IEA989I SLIP TRAP ID=X028 MATCHED.  JOBNAME=DB9GDBM1, ASID=0041.
>  *DSNV086E -DB9G DB2 ABNORMAL TERMINATION REASON=00E80100
>   IEA989I SLIP TRAP ID=X47B MATCHED.  JOBNAME=DB9GMSTR, ASID=0040.
>   IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DB9GMSTR, ASID=0040.
>   IEF450I DB9GDBM1 DB9GDBM1 - ABEND=S028 U REASON=04000200 175
>   TIME=13.51.59
>   IEF404I DB9GDBM1 - ENDED - TIME=13.51.59
>   $HASP395 DB9GDBM1 ENDED
>   DXR110I DJ9G001 STOP COMMAND ACCEPTED
>   IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=0041.
>   IEF450I DB9GMSTR DB9GMSTR - ABEND=S04F U REASON= 180
>   TIME=13.51.59
>   $HASP250 DB9GDBM1 PURGED -- (JOB KEY WAS D18FC9B3)
>   DXR121I DJ9G001 END-OF-TASK CLEANUP SUCCESSFUL - HI-CSA377K  -
>   HI-ACCT-CSA  0K
>   IEF404I DB9GMSTR - ENDED - TIME=13.52.00
>   $HASP395 DB9GMSTR ENDED
>   IEF404I DB9GIRLM - ENDED - TIME=13.52.00
>   IEF352I ADDRESS SPACE UNAVAILABLE
>   $HASP395 DB9GIRLM ENDED
>   IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=0040.
>   IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=003D.
>   $HASP250 DB9GIRLM PURGED -- (JOB KEY WAS D18FC9A7)
>   $HASP250 DB9GMSTR PURGED -- (JOB KEY WAS D18FC99F)
>   DSN3104I -DB9G DSN3EC0X - TERMINATION COMPLETE
>   DSN3100I -DB9G DSN3EC0X - SUBSYSTEM DB9G READY FOR START COMMAND 
> 
> I have also looked at the System Log and the following error messages appear:
> 
> IOEZ1E zFS I / O error 2101520 occurred for aggregate DSN910.SDSNAZF
> IOEZ2E MMRE error id = 31 cis = 11 if = 0 of = 15 buf = 7E4A4000 CI = 0
> BPXF002I FILE SYSTEM DSN910.SDSNAZFS WAS 984 NOT MOUNTED. RETURN CODE =
> 

Re: Problem with startup DB2

2016-11-10 Thread Mark Jacobs - Listserv

Restore the file system from the last good backup would be a good idea.


Hilario Garcia 
November 10, 2016 at 5:53 AM
Hello,

After a hard stop of the partition, DB2 does not start and produces 
the following messages;


-DB9G START DB2
S DB9GMSTR
$HASP100 DB9GMSTR ON STCINRDR
IEF695I START DB9GMSTR WITH JOBNAME DB9GMSTR IS ASSIGNED TO USER START2
, GROUP SYS1
$HASP373 DB9GMSTR STARTED
IEF403I DB9GMSTR - STARTED - TIME=13.51.31
DSNY024I -DB9G DSNYASCP MSTR INITIALIZATION IS STARTING
DSNZ002I -DB9G DSNZINIT SUBSYSTEM DB9G SYSTEM PARAMETERS LOAD MODULE
NAME IS DB9GPARM
DSNZ016I -DB9G DSNZINIT 093
SUBSYSTEM DB9G SYSTEM PARAMETERS ARE AS FOLLOWS:
SYSTEM PARM DSN910.DB9G.SDSNEXIT(DB9GPARM)
DSNHDECP DSN910.DB9G.SDSNEXIT(DSNHDECP)
ACCESS EXIT DSN910.DB9G.SDSNEXIT(DSNX@XAC)
IDAUTH EXIT DSN910.DB9G.SDSNEXIT(DSN3@ATH)
SIGNON EXIT DSN910.DB9G.SDSNEXIT(DSN3@SGN)
DSN7407I -DB9G DSN7GAR1 094
AUTOMATIC RESTART MANAGER REGISTER FAILED.
MVS IXCARM RETURN CODE = 000C,
MVS IXCARM REASON CODE = 0160.
S DB9GIRLM
$HASP100 DB9GIRLM ON STCINRDR
IEF695I START DB9GIRLM WITH JOBNAME DB9GIRLM IS ASSIGNED TO USER START2
, GROUP SYS1
$HASP373 DB9GIRLM STARTED
IEF403I DB9GIRLM - STARTED - TIME=13.51.39
DXR180I DJ9G001 AUTOMATIC RESTART MANAGER IS NOT ENABLED
DXR117I DJ9G001 INITIALIZATION COMPLETE
DSNY001I -DB9G SUBSYSTEM STARTING
IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 103
IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 104
IEC161I DSN910.DB9G.BSDS01.INDEX,USERCAT.Z110.DB2V9
IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 105
IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 106
IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 107
IEC161I DSN910.DB9G.BSDS02.INDEX,USERCAT.Z110.DB2V9
IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 108
IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
DSNJ127I -DB9G SYSTEM TIMESTAMP FOR BSDS= 16.295 08:27:14.61
DSNJ001I -DB9G DSNJW007 CURRENT COPY 1 ACTIVE LOG 110
DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY1.DS02,
STARTRBA=00015180,ENDRBA=0001539B
DSNJ001I -DB9G DSNJW007 CURRENT COPY 2 ACTIVE LOG 111
DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY2.DS02,
STARTRBA=00015180,ENDRBA=0001539B
DSNJ099I -DB9G LOG RECORDING TO COMMENCE WITH 112
STARTRBA=000152F2D000
S DB9GDBM1
$HASP100 DB9GDBM1 ON STCINRDR
SYSTEM ID SYS1 DATE 10/28/2016 2016.302 LINE 6,664 PAGE 2
IEF695I START DB9GDBM1 WITH JOBNAME DB9GDBM1 IS ASSIGNED TO USER START2
, GROUP SYS1
$HASP373 DB9GDBM1 STARTED
IEF403I DB9GDBM1 - STARTED - TIME=13.51.52
DSNY024I -DB9G DSNYASCP DBM1 INITIALIZATION IS STARTING
IEA989I SLIP TRAP ID=X028 MATCHED. JOBNAME=DB9GDBM1, ASID=0041.
*DSNV086E -DB9G DB2 ABNORMAL TERMINATION REASON=00E80100
IEA989I SLIP TRAP ID=X47B MATCHED. JOBNAME=DB9GMSTR, ASID=0040.
IEA989I SLIP TRAP ID=X13E MATCHED. JOBNAME=DB9GMSTR, ASID=0040.
IEF450I DB9GDBM1 DB9GDBM1 - ABEND=S028 U REASON=04000200 175
TIME=13.51.59
IEF404I DB9GDBM1 - ENDED - TIME=13.51.59
$HASP395 DB9GDBM1 ENDED
DXR110I DJ9G001 STOP COMMAND ACCEPTED
IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL, ASID=0041.
IEF450I DB9GMSTR DB9GMSTR - ABEND=S04F U REASON= 180
TIME=13.51.59
$HASP250 DB9GDBM1 PURGED -- (JOB KEY WAS D18FC9B3)
DXR121I DJ9G001 END-OF-TASK CLEANUP SUCCESSFUL - HI-CSA 377K -
HI-ACCT-CSA 0K
IEF404I DB9GMSTR - ENDED - TIME=13.52.00
$HASP395 DB9GMSTR ENDED
IEF404I DB9GIRLM - ENDED - TIME=13.52.00
IEF352I ADDRESS SPACE UNAVAILABLE
$HASP395 DB9GIRLM ENDED
IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL, ASID=0040.
IEA989I SLIP TRAP ID=X33E MATCHED. JOBNAME=*UNAVAIL, ASID=003D.
$HASP250 DB9GIRLM PURGED -- (JOB KEY WAS D18FC9A7)
$HASP250 DB9GMSTR PURGED -- (JOB KEY WAS D18FC99F)
DSN3104I -DB9G DSN3EC0X - TERMINATION COMPLETE
DSN3100I -DB9G DSN3EC0X - SUBSYSTEM DB9G READY FOR START COMMAND


I have also looked at the System Log and the following error messages 
appear:


IOEZ1E zFS I / O error 2101520 occurred for aggregate DSN910.SDSNAZF
IOEZ2E MMRE error id = 31 cis = 11 if = 0 of = 15 buf = 7E4A4000 
CI = 0

BPXF002I FILE SYSTEM DSN910.SDSNAZFS WAS 984
NOT MOUNTED. RETURN CODE = 008A, REASON CODE = EF096058
IOEZ1E zFS I / O error 2101520 occurred for aggregate DSN910.SDSNJCC
IOEZ2E MMRE error id = 31 cis = 11 if = 0 of = 15 buf = 7E4A2000 
CI = 0

BPXF002I FILE SYSTEM DSN910.SDSNJCC WAS 987
NOT MOUNTED. RETURN CODE = 008A, REASON CODE = EF096058

I have tried to run IOEAGSLV with all the options but they give me all 
the following error:


IOEZ1E zFS I / O error 2101520 occurred for aggregate DSN910.SDSNAZFS
IOEZ2E MMRE error id = 31 cis = 12 if = 0 of = 15 buf = 1F8D2000 
CI = 2


Any comments to try to solve the errors and be able to start DB2.

Thank you very much.

Hilario


Problem with startup DB2

2016-11-10 Thread Hilario Garcia
Hello,

After a hard stop of the partition, DB2 does not start and produces the 
following messages;

  -DB9G START DB2
  S DB9GMSTR
  $HASP100 DB9GMSTR ON STCINRDR
  IEF695I START DB9GMSTR WITH JOBNAME DB9GMSTR IS ASSIGNED TO USER START2
   , GROUP SYS1
  $HASP373 DB9GMSTR STARTED
  IEF403I DB9GMSTR - STARTED - TIME=13.51.31
  DSNY024I  -DB9G DSNYASCP MSTR INITIALIZATION IS STARTING
  DSNZ002I -DB9G DSNZINIT SUBSYSTEM DB9G SYSTEM PARAMETERS LOAD MODULE
  NAME IS DB9GPARM
  DSNZ016I  -DB9G DSNZINIT 093
  SUBSYSTEM DB9G SYSTEM PARAMETERS ARE AS FOLLOWS:
SYSTEM PARM  DSN910.DB9G.SDSNEXIT(DB9GPARM)
DSNHDECP DSN910.DB9G.SDSNEXIT(DSNHDECP)
ACCESS EXIT  DSN910.DB9G.SDSNEXIT(DSNX@XAC)
IDAUTH EXIT  DSN910.DB9G.SDSNEXIT(DSN3@ATH)
SIGNON EXIT  DSN910.DB9G.SDSNEXIT(DSN3@SGN)
  DSN7407I  -DB9G DSN7GAR1 094
  AUTOMATIC RESTART MANAGER REGISTER FAILED.
MVS IXCARM RETURN CODE = 000C,
MVS IXCARM REASON CODE = 0160.
  S DB9GIRLM
  $HASP100 DB9GIRLM ON STCINRDR
  IEF695I START DB9GIRLM WITH JOBNAME DB9GIRLM IS ASSIGNED TO USER START2
   , GROUP SYS1
  $HASP373 DB9GIRLM STARTED
  IEF403I DB9GIRLM - STARTED - TIME=13.51.39
  DXR180I DJ9G001 AUTOMATIC RESTART MANAGER IS NOT ENABLED
  DXR117I DJ9G001 INITIALIZATION COMPLETE
  DSNY001I  -DB9G SUBSYSTEM STARTING
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 103
  IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 104
  IEC161I DSN910.DB9G.BSDS01.INDEX,USERCAT.Z110.DB2V9
  IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS1,,,DSN910.DB9G.BSDS01, 105
  IEC161I DSN910.DB9G.BSDS01.DATA,USERCAT.Z110.DB2V9
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 106
  IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
  IEC161I 056-084,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 107
  IEC161I DSN910.DB9G.BSDS02.INDEX,USERCAT.Z110.DB2V9
  IEC161I 062-086,DB9GMSTR,DB9GMSTR,BSDS2,,,DSN910.DB9G.BSDS02, 108
  IEC161I DSN910.DB9G.BSDS02.DATA,USERCAT.Z110.DB2V9
  DSNJ127I  -DB9G SYSTEM TIMESTAMP FOR BSDS= 16.295 08:27:14.61
  DSNJ001I  -DB9G DSNJW007 CURRENT COPY 1 ACTIVE LOG 110
  DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY1.DS02,
  STARTRBA=00015180,ENDRBA=0001539B
  DSNJ001I  -DB9G DSNJW007 CURRENT COPY 2 ACTIVE LOG 111
  DATA SET IS DSNAME=DSN910.DB9G.LOGCOPY2.DS02,
  STARTRBA=00015180,ENDRBA=0001539B
  DSNJ099I  -DB9G LOG RECORDING TO COMMENCE WITH 112
  STARTRBA=000152F2D000
  S DB9GDBM1
  $HASP100 DB9GDBM1 ON STCINRDR
SYSTEM ID SYS1 DATE 10/28/2016 2016.302 LINE   6,664  PAGE   2
  IEF695I START DB9GDBM1 WITH JOBNAME DB9GDBM1 IS ASSIGNED TO USER START2
   , GROUP SYS1
  $HASP373 DB9GDBM1 STARTED
  IEF403I DB9GDBM1 - STARTED - TIME=13.51.52
  DSNY024I  -DB9G DSNYASCP DBM1 INITIALIZATION IS STARTING
  IEA989I SLIP TRAP ID=X028 MATCHED.  JOBNAME=DB9GDBM1, ASID=0041.
 *DSNV086E -DB9G DB2 ABNORMAL TERMINATION REASON=00E80100
  IEA989I SLIP TRAP ID=X47B MATCHED.  JOBNAME=DB9GMSTR, ASID=0040.
  IEA989I SLIP TRAP ID=X13E MATCHED.  JOBNAME=DB9GMSTR, ASID=0040.
  IEF450I DB9GDBM1 DB9GDBM1 - ABEND=S028 U REASON=04000200 175
  TIME=13.51.59
  IEF404I DB9GDBM1 - ENDED - TIME=13.51.59
  $HASP395 DB9GDBM1 ENDED
  DXR110I DJ9G001 STOP COMMAND ACCEPTED
  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=0041.
  IEF450I DB9GMSTR DB9GMSTR - ABEND=S04F U REASON= 180
  TIME=13.51.59
  $HASP250 DB9GDBM1 PURGED -- (JOB KEY WAS D18FC9B3)
  DXR121I DJ9G001 END-OF-TASK CLEANUP SUCCESSFUL - HI-CSA377K  -
  HI-ACCT-CSA  0K
  IEF404I DB9GMSTR - ENDED - TIME=13.52.00
  $HASP395 DB9GMSTR ENDED
  IEF404I DB9GIRLM - ENDED - TIME=13.52.00
  IEF352I ADDRESS SPACE UNAVAILABLE
  $HASP395 DB9GIRLM ENDED
  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=0040.
  IEA989I SLIP TRAP ID=X33E MATCHED.  JOBNAME=*UNAVAIL, ASID=003D.
  $HASP250 DB9GIRLM PURGED -- (JOB KEY WAS D18FC9A7)
  $HASP250 DB9GMSTR PURGED -- (JOB KEY WAS D18FC99F)
  DSN3104I -DB9G DSN3EC0X - TERMINATION COMPLETE
  DSN3100I -DB9G DSN3EC0X - SUBSYSTEM DB9G READY FOR START COMMAND


I have also looked at the System Log and the following error messages appear:

IOEZ1E zFS I / O error 2101520 occurred for aggregate DSN910.SDSNAZF
IOEZ2E MMRE error id = 31 cis = 11 if = 0 of = 15 buf = 7E4A4000 CI = 0
BPXF002I FILE SYSTEM DSN910.SDSNAZFS WAS 984
NOT MOUNTED. RETURN CODE = 008A, REASON CODE = EF096058
IOEZ1E zFS I / O error 2101520 occurred for aggregate DSN910.SDSNJCC
IOEZ2E MMRE error id = 31 cis = 11 if = 0 of = 15 buf = 7E4A2000 CI = 0
BPXF002I FILE SYSTEM DSN910.SDSNJCC WAS 987
NOT MOUNTED. RETURN CODE = 008A, REASON CODE = EF096058

I have tried to run IOEAGSLV with all the options but they give me all the 
following error:

IOEZ1E zFS I / O error 2101520 occurred for aggregate DSN910.SDSNAZFS
IOEZ2E MMRE error id = 31 cis = 12 if = 0 of = 15 buf = 1F8D2000 CI = 2

Any comments to try to solve the errors and be able to start DB2.

Thank