Continuous Batch Process

[Chris Kelleher]

Hi peggers,
As always, MFG/pro 8.6e progress 8.3a04 Nt, and HP-UX
the question.
I am attempting to create a continuos batch process for users to submit there reports through so as not to hold up their sessions waiting for a report to complete before the continue to the next function. I have set up batches that run through corn on my HP-UX box. I have been following the documentation in the QAD Knowledgebase, Doc# 9500277 Tech Note #27.0. I don't quite understand Step 6. I'm not sure what my start-up script is, or where it's located. If anyone has an example of this, I'd appreciate the help. Or, maybe if someone has a more recent document they can point me to. Thanks gang.

David L. Knowles
UNIX Administrator
Captive Plastics, Inc
Partners in Plastics Packaging

 

[Chris Kelleher]

David --

The confusion here is that the Tech Note seems to assume that all clients
are running on UNIX.

Since your clients run on NT, you don't have these 'start up' scripts. So
you need to create one from scratch.

You need environment variables for:

DLC
PROPATH
(at a minimum)

and a PROGRESS client startup line:

$DLC/bin/mbpro <database references or parameter file name> -p <
batch program>
(with standard out/standard error redirected to a file)


HTH. Let the list know if you need more detailed information.

John Nisbet
Kilcreggan Systems and Software, Inc.
QAD Service Alliance Partner
1191 Chestnut Street Suite 2-6
Newton, MA 02464-1351
jnisbet@kilcreggan.com
(617) 969-5432 x201

 

[Chris Kelleher]

Hello,

Since you have a Progress NT client version, you can run the batch
session in your NT Server. I call the continuous batch process as
hotbatch. Here is the detail:

1. Start up script, C:\MRPbatch\hotbatch.pf
-db mfgpro -H server -S mfgport -N TCP -trig TRIGGERS
-db history -ld histdb -H server -S hstport -N TCP -trig TRIGGERS
-db gui -ld qadgui -H server -S gui -N TCP
-cpinternal iso8859-1 -cpcoll basic -Bt 350 -c 30
-D 100 -mmax 8192 -nb 200 -s 48 -p mf.p

2. C:\MRPbatch\batch.p compiled with progress CHR
INPUT from batchin.inp.
/* OUTPUT to batchout.out.*/
PAUSE 0 BEFORE-HIDE.
RUN MF.P.
INPUT CLOSE.
/* OUTPUT CLOSE. */

3. In MfgPro create batch id = hotbatch

4. C:\MRPbatch\batchin.inp (run repeat every 60 seconds).
"Mfguser" "userpass"
"mgbatch.p"
"hotbatch" - - - - - - - - - "YES" "60"
.
.
"Y"

5. Install hotbatch as an NT service (need nt resource kit):
D> CD\ntreskit
D> INSTSRV HotBatchSvc d:\ntreskit\srvany.exe

set as manual or automatic start via Control Panel Services

RUN REGEDT32.EXE:
- HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\HotBatchSvc.
Edit Add Key: "Parameters" key
- Click folder Parameters above.
- Edit, Add Value: "Application", type REG_SZ,
String: "C:\DLC\BIN\_progres.exe"
- Edit, Add Value: "AppDirectory", type REG_SZ,
String: "C:\MRPbatch\hotbatch"
- Edit, Add Value: "AppParameters", type REG_SZ,
String: "-b -pf C:\MRPbatch\hotbatch.pf -ininame
C:\MRPbatch\progress.chr -p batch.p"

5. Make sure the propath in progress.chr refer the right directory.

6. Now you can start and stop hotbatch client easily with just: net
start HotBatchSvc; to stop: net stop HotBatchSvc. Or schedule it via
"at" command.

Hope this helps.

regards,
Michael R

 

[Chris Kelleher]

One addedum to this may be, as I do not know anything about NT, but on UNIX
we create a FLAG file at the begining of the script

# check for the existance of QADBKFL.PROCESSING
if [ -f /home/as400op/QADBKFL.PROCESSING ]
then
echo "Processing file already exist - job aborted"
exit 52
fi
touch /home/as400op/QADBKFL.PROCESSING
chmod 777 /home/as400op/QADBKFL.PROCESSING
chown as400op:mfgpro /home/as400op/QADBKFL.PROCESSING

and then after the job batch.p is complete we run a cleanup job

"Mfguser" "userpass"
"mgbatch.p"
"QADBKFL" <---- batch id (hotbatch