Re: CRTDTAARA first time run each day after V7R4M0 installed

Thanks,

Will try in the morning. I was hoping to find some way to trace what is
happening.

On Thu, Sep 26, 2019 at 2:17 PM Rob Berendt <rob@xxxxxxxxx> wrote:

I recreated the data area. I'll try it again in the morning.

Suggest you try this in the morning:

TRCJOB SET(*ON)
CRTDTAARA...
TRCJOB SET(*OFF) OUTPUT(*PRINT)
WRKPTFGRP While in there hit F6 to print.
DSPPTF OUTPUT(*PRINT)
DSPJOBLOG OUTPUT(*PRINT)
Use iACS to download all these spool files. If you had the job schedule
entry, add that also.
Zip them together.
Create a case at support.ibm.com and upload that file
At 7.4 it's a pretty safe bet you have support.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Blair Hamren
Sent: Thursday, September 26, 2019 2:06 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx

Subject: Re: CRTDTAARA first time run each day after V7R4M0 installed

CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.


Not sure what all happens overnight. Not an IPL, probably some saves. The
job wait time is 30 seconds and my delays are all over the map, like I
said from 20 - 80 seconds. I don't see any locks in any of the programs

in

the programs, but it also happens if I just create it using a command

line

the first thing in the morning.

On Thu, Sep 26, 2019 at 1:52 PM Rob Berendt <rob@xxxxxxxxx> wrote:

What kind of magic happens in that time period? Save? IPL?
Exclusive lock on the object from something related to your menu
system? Change in how 7.4 handles such an object lock? Does the time
match the interval in RTVJOBA DFTWAIT(&DFT

<https://www.google.com/maps/search/OBA+DFTWAIT(%26DFT?entry=gmail&source=g>
WAIT)?

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Blair Hamren
Sent: Thursday, September 26, 2019 1:47 PM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: CRTDTAARA first time run each day after V7R4M0 installed

CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the sender
and know the content is safe.


I tried looking at the exit points and get the following:

Exit
Exit Point
Point Format Registered Text
QIBM_QCA_CHG_COMMAND CHGC0100 *YES Change command exit

programs

QIBM_QCA_RTV_COMMAND RTVC0100 *YES Retrieve command exit

program

But none of this looks at CRTDTAARA.

I would not expect you to have issues with the speed today since it is
the first time creating it. Try again tomorrow when it already exists
and see if it delays.

Thanks

On Thu, Sep 26, 2019 at 1:41 PM Rob Berendt <rob@xxxxxxxxx> wrote:

Tried this also:

dltDTAARA DTAARA(QGPL/BHAMREN)

Object BHAMREN in QGPL type *DTAARA dele

<https://www.google.com/maps/search/ype+*DTAARA+dele?entry=gmail&source=g>
ted.

CRTDTAARA DTAARA(QGPL/BHAMREN) TYPE(*CHAR) LEN(10) TEXT('Menu')

Data area BHAMREN created in library QGPL.

CRTDTAARA DTAARA(QGPL/BHAMREN) TYPE(*CHAR) LEN(10) TEXT('Menu')

Data area BHAMREN exists in QGPL.

Very fast.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com


-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf
Of Blair Hamren
Sent: Thursday, September 26, 2019 1:29 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: CRTDTAARA first time run each day after V7R4M0 installed

CAUTION: This email originated from outside of the organization. Do
not click links or open attachments unless you recognize the sender
and know the content is safe.


CRTDTAARA is running slow the first time it is called each day. The
only thing that seems different is that we upgraded to V7R4M0. Is
anyone else seeing this?

Here is how it works. Our menu program creates a data area with our
environment values every time it is called. We monitor for message
CPF1023 and just ignore it if it already exist (no big deal if it
does and it normally already exists for existing users).

The problem comes the first time I run the menu each day. Going
through debug it is always hung up on the CRTDTAARA command. I have
taken this a step further and just called this command from a
command line each day with the same results. This morning the
command hung my session for 80 seconds before the CPF1023 message
came back. Every other time I run it, the reply is instant.

Here is the command:

CRTDTAARA DTAARA(QGPL/BHAMREN) TYPE(*CHAR) LEN(10) TEXT('Menu')

Like I said, when I call it from a command the first time each day
it hangs for a while (it has been from 15 - 80 seconds) before it
comes back with the message of "Data area BHAMREN exists in QGPL."
Our menu program monitors for this message but it still hangs up the
first time

every day.

The odd thing is that I can sign off and sign back on later in the
day and there is no delay in the response. But the next day when I
sign on the delay is there again.

Can someone on a V7R4M0 machine create a data area and then try it
again the next day and see if there is a delay? Try it over a few
days

even.

The only thing that we can see is the installation of the new
operating system, but maybe someone has seen this for a different

reason.

Thanks!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our
affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To
subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To

subscribe,

unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com