Since the Journal Status Monitor can't run without the batch server, and since shutting down the batch server without first shutting down the JSM creates hung JSM entries which end up causing support problems... why not have the Batch Server tweaked so when it starts it automatically executes a delete of all ABATRQT records that match left$(TACHE,8)="ACCBATCH", and then on the BATCH table set STA=0 where COD=”ACCENTRY”.
This would head off unnecessary support calls and save partners from committing time to a non-value-added task.
by: Glenn C. | over a year ago | Technical
Comments
useful info
Along these lines there is a general/user parameter that can be set that will automatically restart the batch server in the event that it is shutdown when a user logs into the system. Could this functionality be extended to also restart the Accounting Tasks?
While I do agree that it would be nice if the Accounting Task could be auto-started from within X3 in a similar way to how the batch server can be started, users should also know that it's also possible to use a batch file to auto-start both the batch server and the accounting task:
StartX3BatchServer.bat
-----------------------
SET ADXDIR=C:\SAGE\X3V6\runtime
SET ADXGEN=TRUE
SET TMPDIR=%ADXDIR%\tmp
SET SHELL=%SystemRoot%\System32\CMD.exe
SET AE_SERVICE=1806
SET AE_SERVICE_NAME=X3V6
SET AE_SERVICE_DEST=C:\WINNT\System32\
SET AE_SERVICE_FORMAT=ADXD.bat
SET PATH=C:\Program Files\Microsoft SQL Server\100\Tools\binn;C:\SAGE\X3V6\runtime\bin;C:\SAGE\X3V6\runtime\ebin;C:\SAGE\X3V6\runtime\lib;%PATH%
SET DATASOURCE=X3V6
SET SQLS7_SID=x3v6
SET SQLS7_OSQL=C:\Program Files\Microsoft SQL Server\100\Tools
SET STUSIZE=3
SET NLS_SORT=BINARY
SET DOSS_REF=X3
SET DBVER=10
set EXE_OSQL="C:\Program Files\Microsoft SQL Server\100\Tools\Binn\osql"
set DB_NAM=sagex3001\X3V6
set REP_TMP="%ADXDIR%\tmp"
set REP_RUN="%ADXDIR%"
set REP_DAT=C:\SAGE\X3V6\database\data
C:\Users\sagex3>copy c:\accbatch.job c:\sage\x3v6\folders\NADEMOPRM\batch\start\accbatch.job
echo BATCH SERVER STARTED - IT IS SAFE TO CLOSE THIS WINDOW!
c:\sage\x3v6\runtime\bin\adonix -a -l ENG SERVX3
ACCBATCH.JOB
--------------------
DOSSIER=NADEMOPRM
UTIL=ADMNA
PASSE=9B8E36ADE34FAD4002A67E5C
GRP=
TACHE=ACCBATCH
DATE=20120801
HEURE=1329
Unfortunately, if the accounting task has gone through too many 'ungraceful' shutdowns then there's a good chance that it won't come up correctly in any case. Sure would be nice if the batch server would clear those hung JSM entries for us when it was starting..... ;-)
Sage - this may not be receiving votes, but isn't it just one of those things that you "just do"? Lets create a self supporting system instead of one that requires attention and fixing. Can we please eliminate the unnecessary annoyance? How hard would it be to make the batch server check all folders and clean the hung entries during its startup sequence?
It seems it has an official solution as well https://support.na.sage.com/selfservice/viewContent.do?externalId=16965&sliceId=1