Netview subtasks not started

Madhaviy · New User Joined: 30 Oct 2009 Posts: 37 Location: India

Hi,

When NETVIEW was started after IPL there was no message for 45 mins after the start message.

Normally the Netview messages are:
23.14.55 STC02054 IEF695I START NETVIEW WITH JOBNAME NETVIEW
23.14.55 STC02054 $HASP373 NETVIEW STARTED
23.14.55 STC02054 IEF403I NETVIEW - STARTED - TIME=23.14.55
23.14.57 STC02054 BNJ080I BNJLINTB - BUFFER SIZE=24K,SLOT SIZE
23.14.57 STC02054 DSI244I NETVIEW TRACE ACTIVE FOR TASK = ALL

The BNJ080I usually follows the IEF403I message

However i got:

02.12.34 STC06227 IEF695I START NETVIEW WITH JOBNAME NETVIEW
02.12.34 STC06227 $HASP373 NETVIEW STARTED
02.12.34 STC06227 IEF403I NETVIEW - STARTED - TIME=02.12.34
02.58.01 STC06227 IEB133I MINIMUM REQUESTED STORAGE (280K) NOT AVAILABLE
02.58.03 STC06227 BNJ080I BNJLINTB - BUFFER SIZE=24K,SLOT SIZE=2
02.58.03 STC06227 DSI244I NETVIEW TRACE ACTIVE FOR TASK = ALL :

If IEB.. were the problem it should have come earlier,,

Due to this the tasks like CNM60 activated late and caused other problems..
Not able to figure out what was holding it for 45 mins..
Please suggest.

Thank you,

PeterHolland · Posted: Mon Jul 26, 2010 4:20 pm

IEB133I is an IEBCOPY message. That has nothing to do with NETVIEW.
Why was the IPL executed? Changes applied? If yes, where ?
Maybe a NETVIEW rexx was started doing strange things.
BMC started by NETVIEW? (IEB133I MINIMUM REQUESTED STORAGE NOT AVAILABLE
This problem was caused by an OEM vendor (BMC)
(Product DATA ACCELERATOR NON VSAM).
The eyecatcher was DPOCOPY csect in DPOMOCOPY.

. Resolution: BMC fix number - P281547
for version 1.0.04 and
for version 1.0.05)?

Questions, questions.

Madhaviy · New User Joined: 30 Oct 2009 Posts: 37 Location: India

Hi

IPL was a regular monthly outage.
There were DASD movements before the IPL. Thats it.
There were no other changes.

We do not have any BMC product running.

Thankyoul,

Madhaviy · New User Joined: 30 Oct 2009 Posts: 37 Location: India

it was observed in between

02:42:09.16 INTERNAL 00000090 SSS00087 NETVIEW WAITING FOR ==> INITIALIZATION MESSAGE

02:42:16.64 AFOC0006 00000094 SSS00065 NETVIEW ==> STARTING UP UP

PeterHolland · Posted: Mon Jul 26, 2010 5:08 pm

OK, thats clear.

Any strange commands entered at the outstanding NETVIEW replay?
Any exceptional messages in the syslog/netlog/joblog?

I/we really need more info, to say something usefull.

Madhaviy · New User Joined: 30 Oct 2009 Posts: 37 Location: India

Is there a possility that Netview initialization depends on a tape..

When searched in RMF III:
between 2.12 and 2.58 following was displayed:
Job:Netview Primary Delay:Job awaiting service from HSM.
Probable cause: Dataset recall from auxiliary storage.

Thank you,

PeterHolland · Posted: Mon Jul 26, 2010 7:17 pm

I think you answered your own question.
Now you have to ask your storage people which storage was needed
and most important why?
Or maybe a change was applied to the NETVIEW started task procedure?

Madhaviy · New User Joined: 30 Oct 2009 Posts: 37 Location: India

If i could know what does Netview requires for initialization as netview is not throwing any message between that time,
And there is lot of HSM activity going on that time..so its difficult to find what is ours..
also no changes were applied to Netview proc..

PeterHolland · Posted: Mon Jul 26, 2010 8:52 pm

Netview (as far as i remember) is giving a lot of messages.
But its still your IT department that have to give information.

I cant help you further.

Madhaviy · New User Joined: 30 Oct 2009 Posts: 37 Location: India

i can see at that particular time HSM is recalling a tape..
and recall is completed just before the Netview initialization completes:

02.56.00 STC06157 *IEC501A M C00E,C30227,SL,,HSM,HSM,HSMMIG.HMIGTAPE.DATASET
02.58.06 STC06157 IEF234E K C00E,C30227,PVT,HSM,HSM

from CA VTAPE:
02:57:59.67 STC06274 00000090 SVT1P0401I C30227 recall completed successfully

Also,
we in Netview JCL the second step is a IEBCOPY compress and has two datasets.

Now if we can establish that:
1.) Netview has trigerred the HSM recall;or
2.) Any one of the datasets is recalled at that particular time.
we can blame HSM for the delay.

Thank you,

PeterHolland · Posted: Mon Jul 26, 2010 9:05 pm

No, HSM is not to blame.
To blame are the people that f.upped your NETVIEW procedure.
I never did see (and i did some NETVIEW/SA390) work a NETVIEW procedure with an IEBCOPY step in it.
But then maybe people i worked with, and they with me knew how to
work with NETVIEW and all that stuff connected with NETVIEW.

Nevertheless, it was a nice conversation.

Madhaviy · New User Joined: 30 Oct 2009 Posts: 37 Location: India

okie.. if you think so..