|
Thanks for all the research and information! I was able to finally get it to work on our end just prior to receiving your feedback. The current task for batch allocation on our end (which is not Style) is OE 03 task 3100. It included an interactive program (to prompt for the stockroom) and a batch program (which was submitted by AM). I simply created a new task which was tied to a custom batch CL program. This CL program set the stockroom to the LDA as expected by OE320CLP (batch allocation)... then called OE320CLP directly. It seems to work fine with the exception that Machine Manager always seems to think the job ends abnormally. I have checked the database results, and it seems to work fine! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ At 08:59 PM 2/4/98 -0500, you wrote: > > >---------- >> From: Robert A. Rogerson <rogerson@interlog.com> >> To: JBAUSERS-L@midrange.com >> Subject: Re: JBA Batch Jobs >> Date: Tuesday, February 03, 1998 9:30 PM >> >> Hi Jim, back again... >> >> I only have access to the style version of the software at present but it >> should be similar to then base software. In style the batch allocation >> program (AP315) is called from the task. More than likely there is a >> similar OE315 program. >> >> When this task is investigated there is only a interactive program. This >> program prompts the user for the desired allocation parameters and then >> submits the actual batch program AP320CLP (probably OE320CLP with non >style >> versions). As this set up stands the task can not be scheduled. There >> must be a batch program in order to schedule the task. >> >> In order to allow this job to be scheduled AP315/OE315 requires >> modification to separate the prompt screen for the submission of the >batch >> job. In our case a new program AP315U was created whi9ch had the sole >> function of displaying a screen to receive the user's parameters and >update >> the LDA with these values. The actual submission of the batch program >was >> moved to the task and AP320CLP/OE320CLP now became the batch job for a >new >> task which was created in the customer environment. Below is a snippet >of >> the code modification that was needed to implement the previous steps. >> >> H 1 Y >> ***************************************************************** >> * * >> * SYSTEM NAME - JBA APPAREL * >> * * >> * PROGRAM NAME - AP315 * >> * * >> * WRITTEN BY - G.JOHNSON * >> * * >> * DATE - APRIL 1990 * >> * * >> * PROGRAM DESCRIPTION - SELECT FOR BATCH ALLOCATION * >> * * >> ***************************************************************** >> /EJECT >> ***************************************************************** >> * MODIFICATION CONTROL Scan on FIX NO * >> * ~~~~~~~~~~~~~~~~~~~~ * >> * * >> * FIX NO. BY DATE DESCRIPTION * >> * ~~~~~~~~ ~~ ~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ * >> * DSI001 JXH 03/09/90 ALLOW ALLOCATION OF FULL PRODUCT * >> * CODES WITH SCALING FACTORS * >> * * >> * STV2_39 CM2 1 Oct 93 Looping on F8 from scaling factor * >> * for full item level * >> * * >> * ISS001 RAR 02/10/97 Change program so that the CL program* >> * AP320CLP is not submitted by this * >> * program but is the batch program * >> * for Task 9020. * >> * * >> ***************************************************************** >> .... >> .... Code here... >> .... >> * Remove the submission of AP320CLP from this programISS001 >> * and add it to task ST HAN 03 9020. ISS001 >> C* >> C* >> C* SUBMIT BATCH ALLOCATION JOB >> *----------------------------------------------------ISS001 >> C*--------------------MOVEL'BATCHALL'L#JOBN-----------ISS001 >> C*--------------------MOVE-'OC'------L#JOBN-----------ISS001 >> C*--------------------MOVE-*BLANKS---L#PGID-----------ISS001 >> C*--------------------MOVEL'AP320CLP'L#PGID-----------ISS001 >> C*--------------------OUT--LDA------------------------ISS001 >> C*--------------------CALL-'XA902'--------------------ISS001 >> C*--------------------IN---LDA------------------------ISS001 >> C*----------L#RTCD----CASEQ'**'------*PSSR------------ISS001 >> C*----------L#RTCD----CASEQ'S*'------*PSSR------------ISS001 >> C*--------------------END-----------------------------ISS001 >> C MOVE ' Y' L#RTCD ISS001 >> C OUT LDA ISS001 >> C MOVE *ON *INLR ISS001 >> C RETRN ISS001 >> E002 C END >> C GOTO MAIN10 >> E001 C END >> /EJECT >> >> Sorry about the alignment but you know it is with non proportional >fonts... >> >> This was the only modification required in the interactive program. The >> important thing is that L#RTCD is updated to ' Y' in the LDA before the >> program ends. This indicated to Business400 to continue and submit the >> batch program portion of the task. The new task is as follows: >> >> XA330 Interactive Program Generator System: >> HANES >> Maintain Tasks > >> >> Application Task code Action > >> >> ST HAN 03 9020 *UPDATE BESPOKE >TASK >> >> Type changes, press Enter > >> >> > >> >> Description Batch Allocation > >> >> > >> >> Interactive program to process request . . AP315U > >> >> Batch program to process request (if any) . AP320CLP > >> >> Job name (if batch program) . . . . . . . . BATCHALLOC > >> >> Initial return code for option . . . . . . > >> >> Exclusivity . . . . . . . . . . . . . . . . Shared Use of Company > >> >> Exclusivity group . . . . . . . . . . . . . > >> >> Sub-task, Function List, Report Generator . 0 (0=Task, 1=Sub, 2=IPG >> List, >> Recovery program . . . . . . . . . . . . . 3=Rep Gen, >> 4=Rati) >> Pre-processing program . . . . . . . . . . > >> >> Library list . . . . . . . . . . . . . . . Blank for default > >> >> > >> >> Task Job Queue/Library . . . . . . . . . . / > >> >> Task Print Queue/Library . . . . . . . . . PRT01 / QUSRSYS > >> >> Hold on Output Queue . . . . . . . . . . . 0 (1=Yes 0=No) > >> >> F3=Exit F4=Browse F11=Delete F12=Previous F19=Where used > >> >> F14=Task class F20=Task exclusivity > >> >> >> Remember that Hanes is using the style version of JBA software and AP >> programs more than likely relate to the same OE programs. >> >> I hope this solves your problem. If not send me more details. Why JBA >> sometimes submits jobs from interactive program and sometimes through the >> batch portion of a task remains a mystery and may remain a mystery like >> that of the Loch Ness monster. As for the comment from the JBA help line >> that this strategy won't work maybe they should turn their attention to >> solving the mystery of Nessy. (Just kidding). I think you will find >this >> works. Again, if not let me know and I'll help you solve it. >> >> Rob Rogerson > >+--- >| This is the JBA Software Users Mailing List! >| To submit a new message send your mail to "JBAUSERS-L@midrange.com". >| To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. >| Questions should be directed to the list owner: doug333@aol.com. >+--- > > ****************************** Jim Sehi Sr. Programmer/Analyst Hach Company 5600 Lindbergh Drive Loveland, Colorado 80538 Email: jsehi@hach.com Phone: 970-663-1377 x2538 Fax: 970-669-2932 ****************************** +--- | This is the JBA Software Users Mailing List! | To submit a new message send your mail to "JBAUSERS-L@midrange.com". | To unsubscribe from this list send email to JBAUSERS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: doug333@aol.com. +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
