J31410 eating up resources (fwd)

Guest

Guest
Date: Wed, 18 Oct 2000 09:54:09 -0400
From: ahenry@hemlomines.com
To: jdeworld@jdelist.com
Subject: J31410 eating up resources

Hi,

We are on A7.3 cum 8. We run program J31410 (Print
Pick List), which prints,
directly to the warehouse, the parts required to
complete the w.o..

The problem I'm experiencing, is with the amount of
time (and resources) that it
takes to complete this job. Every time the program
runs, it indexes a file,
which takes up to 95% of the time required.

I have asked JDE if there was a way around having to
index the file every time,
but I got the usual run around and finally my answer
was basically "NO".

Does anyone run this program, and if so, has anyone
figured out how to get
around the indexing every time.

I wrote a lot of programs, and none of them index the
logical files that they
use. I don't understand why that program has to.

Our maintenance guys call this program and expect that
whenever they get to the
warehouse, all their parts are and waiting for them.
But what happens, is each
job takes anywhere from 10 to 15 minutes to complete
(and longer if the system
is slow), and if several jobs are in the jobq at the
same time, the warehouse
might not see the report for easily over an hour, which
in turn slows down the
repair time.


I just realized that I talk (type) too much.

Thanks,

Andre Henry
M.I.S. Tech.
Williams Operating Corporation
Phone (807) 238-1100 ext. 4256
Fax (807) 238-1050
e-mail ahenry@hemlomines.com


----- End forwarded message -----
 

G_Smith

Well Known Member
A couple of things that you can check on.

1) If program is using logical file, is the logical file Access Path
Maintenance option set to anything but *IMMED. If it is *DLY or *REBLD then
the access path would have to be maintained each time it is used. Not seen
too often but every once in a while someone will attempt to save cpu cycles
and change or build a logical without *IMMED Access Path Maintenance.

2) If the indexing is as a result of the DW Data Sequence Options being
such that there isn't a path anywhere near the order of the DW then the
system will have to take time to build one every time the program is run.
One solution is to create a "speed-up logical", that is create a logical
path that mirrors the Data Sequence Options of the primary DW that is run
for the process. This logical will never be accessed but the access path
will be used by any "query" (i.e. OPNQRYF) that uses the same order of the
data records and for a file with many records, the results are outstanding.
Of course their are people who don't want additional access paths for the
system to maintain but if you have an important process that requires better
response time then this is again worth the trade-off.

George Smith
Sr. Programmer/Analyst
email: smithg@walcointl.com
Walco International
Grapevine, TX


>

George Smith
Walco International, Inc.
 

sdollard

Active Member
my question would be is how are you sorting in your dreamwriter. The index is
taking so long because it can not find a logical file keyed the same as the
sort in the dreamwriter, so it has to create a new one every time it runs.
Also, could just be your box is slow??

Steve
 

dkazinski

Member
Hi,
Edwards has a sar which basically tells you how to create two new logicals
which as they state will help the processing time. I applied the sars and in
fact the time increased. We have a division here that modified the program to
reference two custom mods which dramatically decreased the run time. But, for
now I would get to the JDE web site and look for the sars under P31410 or P31415
and apply those. Hope it works for you.





support28 <ahenry@hemlomines.com> on 10/19/2000 10:36:50 AM

Please respond to jdeworld@jdelist.com

To: jdeworldml@jdelist.com
cc: (bcc: Debbie Kazinski/FLECKHQ/PENTAIR/US)
Fax to:
Subject: J31410 eating up resources (fwd) ~~0:19



Date: Wed, 18 Oct 2000 09:54:09 -0400
From: ahenry@hemlomines.com
To: jdeworld@jdelist.com
Subject: J31410 eating up resources

Hi,

We are on A7.3 cum 8. We run program J31410 (Print
Pick List), which prints,
directly to the warehouse, the parts required to
complete the w.o..

The problem I'm experiencing, is with the amount of
time (and resources) that it
takes to complete this job. Every time the program
runs, it indexes a file,
which takes up to 95% of the time required.

I have asked JDE if there was a way around having to
index the file every time,
but I got the usual run around and finally my answer
was basically "NO".

Does anyone run this program, and if so, has anyone
figured out how to get
around the indexing every time.

I wrote a lot of programs, and none of them index the
logical files that they
use. I don't understand why that program has to.

Our maintenance guys call this program and expect that
whenever they get to the
warehouse, all their parts are and waiting for them.
But what happens, is each
job takes anywhere from 10 to 15 minutes to complete
(and longer if the system
is slow), and if several jobs are in the jobq at the
same time, the warehouse
might not see the report for easily over an hour, which
in turn slows down the
repair time.


I just realized that I talk (type) too much.

Thanks,

Andre Henry
M.I.S. Tech.
Williams Operating Corporation
Phone (807) 238-1100 ext. 4256
Fax (807) 238-1050
e-mail ahenry@hemlomines.com


----- End forwarded message -----




--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=19
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
Discover how to build no-code data integrations and business process automations.

ahenry

Member
Re:RE: J31410 eating up resources (fwd)

Hi George,

I checked the DW, and the main file is F4801.
So I looked at the DW sorting and created a logical file to match the sort.
WADOCO/WALOCN

I ran the program and see that the file that takes so long to index is F3111LD.


I check F3111LD and found that it was built with *immed Access Path
Maintenance.

Maybe your idea about building and extra logical is still good, but I would have
to figure out why it's always picking on F3111LD.

Andre Henry

____________________Reply Separator____________________
Subject: RE: J31410 eating up resources (fwd) ~~19:25
Author: <jdeworld@jdelist.com>
Date: 10/19/2000 8:59 AM

A couple of things that you can check on.

1) If program is using logical file, is the logical file Access Path
Maintenance option set to anything but *IMMED. If it is *DLY or *REBLD then
the access path would have to be maintained each time it is used. Not seen
too often but every once in a while someone will attempt to save cpu cycles
and change or build a logical without *IMMED Access Path Maintenance.

2) If the indexing is as a result of the DW Data Sequence Options being
such that there isn't a path anywhere near the order of the DW then the
system will have to take time to build one every time the program is run.
One solution is to create a "speed-up logical", that is create a logical
path that mirrors the Data Sequence Options of the primary DW that is run
for the process. This logical will never be accessed but the access path
will be used by any "query" (i.e. OPNQRYF) that uses the same order of the
data records and for a file with many records, the results are outstanding.
Of course their are people who don't want additional access paths for the
system to maintain but if you have an important process that requires better
response time then this is again worth the trade-off.

George Smith
Sr. Programmer/Analyst
email: smithg@walcointl.com
Walco International
Grapevine, TX


>

George Smith
Walco International, Inc.
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=25
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

dkazinski

Member
Re:RE: J31410 eating up resources (fwd)

Hi,
J31410 calls P31415 and its based on file is the f3111. When you see the
index on the F3111LD, it's because P31415 is running. You should look at the
dw version for P31415 and maybe consider creating another logical for the F3111
or applying the sar that Edwards supplies.





ahenry <ahenry@hemlomines.com> on 10/19/2000 12:35:19 PM

Please respond to jdeworld@jdelist.com

To: jdeworldml@jdelist.com
cc: (bcc: Debbie Kazinski/FLECKHQ/PENTAIR/US)
Fax to:
Subject: Re:RE: J31410 eating up resources (fwd) ~~19:39



Hi George,

I checked the DW, and the main file is F4801.
So I looked at the DW sorting and created a logical file to match the sort.
WADOCO/WALOCN

I ran the program and see that the file that takes so long to index is F3111LD.


I check F3111LD and found that it was built with *immed Access Path
Maintenance.

Maybe your idea about building and extra logical is still good, but I would have
to figure out why it's always picking on F3111LD.

Andre Henry

____________________Reply Separator____________________
Subject: RE: J31410 eating up resources (fwd) ~~19:25
Author: <jdeworld@jdelist.com>
Date: 10/19/2000 8:59 AM

A couple of things that you can check on.

1) If program is using logical file, is the logical file Access Path
Maintenance option set to anything but *IMMED. If it is *DLY or *REBLD then
the access path would have to be maintained each time it is used. Not seen
too often but every once in a while someone will attempt to save cpu cycles
and change or build a logical without *IMMED Access Path Maintenance.

2) If the indexing is as a result of the DW Data Sequence Options being
such that there isn't a path anywhere near the order of the DW then the
system will have to take time to build one every time the program is run.
One solution is to create a "speed-up logical", that is create a logical
path that mirrors the Data Sequence Options of the primary DW that is run
for the process. This logical will never be accessed but the access path
will be used by any "query" (i.e. OPNQRYF) that uses the same order of the
data records and for a file with many records, the results are outstanding.
Of course their are people who don't want additional access paths for the
system to maintain but if you have an important process that requires better
response time then this is again worth the trade-off.

George Smith
Sr. Programmer/Analyst
email: smithg@walcointl.com
Walco International
Grapevine, TX


>

George Smith
Walco International, Inc.
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=25
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************






--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=39
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

ahenry

Member
Re:RE: J31410 eating up resources (fwd)

Hi List,

And thank you list.

The problem with program P31410 indexing a logical file every time has been
solved.

Program P31410 calls P31415. P31415 was guilty of using file F3111LD which
wasn't that close to the key fields required by the DW.

I created a new logical for F3111 and changed it the DWV, and the program ran in
20 seconds instead of 5 to 10 minutes.

Thanks again Richard & George.

Andre Henry





Andre Henry

____________________Reply Separator____________________
Subject: RE: J31410 eating up resources (fwd) ~~19:25
Author: <jdeworld@jdelist.com>
Date: 10/19/2000 8:59 AM

A couple of things that you can check on.

1) If program is using logical file, is the logical file Access Path
Maintenance option set to anything but *IMMED. If it is *DLY or *REBLD then
the access path would have to be maintained each time it is used. Not seen
too often but every once in a while someone will attempt to save cpu cycles
and change or build a logical without *IMMED Access Path Maintenance.

2) If the indexing is as a result of the DW Data Sequence Options being
such that there isn't a path anywhere near the order of the DW then the
system will have to take time to build one every time the program is run.
One solution is to create a "speed-up logical", that is create a logical
path that mirrors the Data Sequence Options of the primary DW that is run
for the process. This logical will never be accessed but the access path
will be used by any "query" (i.e. OPNQRYF) that uses the same order of the
data records and for a file with many records, the results are outstanding.
Of course their are people who don't want additional access paths for the
system to maintain but if you have an important process that requires better
response time then this is again worth the trade-off.

George Smith
Sr. Programmer/Analyst
email: smithg@walcointl.com
Walco International
Grapevine, TX


>

George Smith
Walco International, Inc.
--------------------------
Visit the forum to view this thread at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=W&Number=25
*************************************************************
This is the JDEList World Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 
Top