Beruflich Dokumente
Kultur Dokumente
Web 7
Contents Page
6.8 POS-EoD..................................................................................................................................... 22
6.1 System End-of-Day This function will initiate the End-of-Day procedure
6.3 Print EoD Reports This function shows the following subitem
Print EoD Spoolfile
Print old EoD Spoolfiles
Print DOS EoD
6.7 Re-Run EoD Due to hardware problems the End-of-Days might have to be
performed as exception at the server. The Re-Run EoD function will
process these End-of-Days at a later date in order to update all files.
6.8 POS-EoD This function can be only started if the Server is set for Auto-End-of-
day (24 hour store). See also AS@R docu Sec. 5 - Cluster Sytem.
Therefore, a higher authorization level is used for this button and has
to be changed when the option for 24 hour is set.
When this button is pressed, an End-of-Day request will be initiated.
The system will check if there are still the process running to apply parameters. If the apply
is still in progress, no other parameters can be exported nor the End-of-Day started.
If the settings in param_maint.properties are set to export parameters at End of Day, the first
step will check if there are still parameters at POS Server which are not applied yet. The
message Exporting / Transferring parameters to server will be displayed. Only in case the
system will not continue to the next window, because there might be still parameters not applied,
then cancel this and check for the reason.
When the new parameter export can take place, the system will continue to the following screen:
The field Export Date shows when the system should check for any parameter maintenance
with this data or earlier. Parameter files for the POS Server / POS terminals will be created.
Example:
On Saturday 17.02.2007 is the last End-of-Day before Monday morning.
Parameters might have an activation date of 19.02.2007 and should be active on Monday,
19.02.2007.
In this case the Date for export (= next open day) has to be selected for the
Monday 19. 02. 2007.
The parameter files will be exported from the data base and sent to the POS Server. These
parameters will be available at the POS terminals at Start-of-Day the next day.
The system will be initialized. When the Core is running, then certain checks will now be
performed by the system if the End-of-Day is possible at this moment.
After the export of parameters, the system will check again, if there are still the process
running to apply parameters. If the parameter apply is still in progress, the End-of-Day
cannot be started immediately. Some time has to be waited, then it will be possible to start
the EoD again.
9 Cluster EoD
If a terminal is defective and the locking function cannot be finalized, then the lock can be
released by 4 System Functions / 6 Remove Function Lock.
The following action codes will be accepted by the End-of-Day procedure and have to be
found for each client in the columns Ready for EoD - Online / WebGM / Defect:
AC 02 = Signed out
AC 87 = Define terminal o.k. the same day
AC 88 = Define terminal o.k. the next day
AC 98 = Define terminal defect
AC 99 = This terminal performed already a short End-of-Day;
e.g. POS in the flower shop which closes earlier.
Example:
A checker is still signed-in at POS terminal 011
WebMaster terminal 802 is still in a WebMaster function and not signed out
POS terminal 011 and WebMaster terminal 802 can be informed to close or can be
automatically logged out by pressing the button LogoutWebClients.
This is not possible when the client is performing a GrandMaster function. This has to
be closed locally so that the End-of-Day can be started.
POS terminal 011 has to be signed out at the terminal
The system will check every 5 seconds the status. If someone signs in during at another terminal
during this start, it will be automatically shown in this screen as Not closed.
When all clients are in the blue (online) area the End-of-Day can be started.
The button StartEOD has to be pressed or Alt + S.
Note:
In case the checker is signed out at POS, however, the system is not recognizing the code.
Perform sign in and sign out at the POS terminal and start End-of-Day again.
Online
All POS terminals which worked today must be either in the Online or
in the Defect column.
WebClient
All WebMaster terminals which were online today must be either in the
WebGM or in the Defect column.
Defect
A POS terminal or a WebMaster terminal which had hardware
problems during the day and is shut down, will be shown in the
terminal status as offline. That the terminal data can take part at the
End-of-Day, the terminal must be declared defective. The data of the
POS server will be used for the End-of-Day procedure.
For Define Defective see WebMaster Section 5.
Not closed
The checker/supervisor is still signed in at the POS terminal.
A sign out is required.
Offline
The terminal is either
not within the POS program
is turned off or
is not connected to the LAN
The situation has to be checked and corrected.
If a terminal is defective and therefore turned off, it has to be declared
defective.
Files Mismatch
Data mirroring of this terminal to the server is disabled.
Possible reasons are:
The Server has already POS totals and counters and the terminal
totals were reset and are zero. The Reset Control counter of the
Server M_LANxxx.DAT and the POS CMOS do not match.
The Server has more Item Data Capture records than the terminal
itself.
The Release number of the parameters does not match between
Server M_LANxxx.DAT and POS S_REGxxx.DAT.
The M_LANxxx.DAT shows already an AC 90 - 99 for this terminal
and the terminal tries to get online
The EoD Flag is on (M_LANxxx.DAT Status 08) and the terminal
which has not worked before tries to get online
In any of the above cases, the POS terminal has to be shut down, the
WebMaster terminal has to be disconnected and the POS terminal
has to be declared defective for the End-of-Day. Thus the data of the
server will be taken for the EoD procedure.
Datatransfer
The terminal total mirroring is currently running.
After some seconds the terminal will change its status.
After all checks are performed and it was proofed that all clients are now ready for the End-of-
Day the End-of-Day can start.
A definition in the core.properties for settlement evaluation allows an additional check on checker
unsettled or settled. The End-of-Day can be stopped at this point and it is the decision of the user
to return to cashier settlement functions.
Exit: This will interrupt the End-of-Day and it is possible to perform settlement functions.
Note: An evaluation on Media-Count can be also checked before End-of-Day is performed. The
settings are done in core.properties.
A Web-Terminal can be still signed on; e.g. in PLU maintenance etc., when End-of-Day is
started at End-of-Day-Web-terminal.
The system will check the status every <N> seconds. This value is determined within the
core.properties (property: core.eval.delay).
The client can be informed with the button Inform terminals.
All terminals will be shown in the EOD column and the End-of-Day is started.
Sign-in at another WebClient is possible again, after the End-of-Day is finished.
The End-of-Day is now in progress and performs its steps. When all data and functions are in a
good and normal stage, then the Core will finalize the End-of-Day. It will even continue in the
background, when the browser is stopped.
End-of-Day sequence
41 ArticleDateUpdate
118 UserTrackerReset Reset the user tracker to the new AS@R parameters
The End-of-Day itself is now finished. There are Post-End-of-Day activities following. This
depends on the settings in eod.properties (completion.shutdown=TRUE,
automatic.execution=FALSE etc.)
The standard performs the following functions:
Stop JRE
Stop database
Save database
The database will be saved depending on the configuration of the system. The batch
\web\mtxwm\upd\DB_SAFE.BAT takes care where it will be saved.
either on Backup-Server in \server\safesql if a Backup-Server is defined or
if Backup Server and Database are on the same PC it will be saved on WebMaster PC
in the directory \web\mtxwm\upd\sql.dat
on Primary Server in \server\safesql if no Backup-Server is defined and the POS Server
software is running in a different PC then the WebMaster or
if POS Server, WebMaster and Database are installed in the same PC the database will
be saved in a different directory \web\mtxwm\upd\sql.dat. However, since it is the same
PC the following batch should be activated and modified:
\web\mtxwm\upd\DB_PRE to DB_PRE.BAT. The example shows that e.g. POS 10 will
be used to safe the DB.
set dest=\\REG010\c$
set dest_path=sql.dat
Thus the database can be saved to a different device within the LAN.
SW-Update will take place to all parts of the system POS terminal, POS Server, WebMaster,
DB if available
Database is started
JRE is started
Login screen will be shown
Also a combination of End-of-Day and e.g. ReRun EoD or System Init is not possible at the
same
time.
Example JavaPOS:
At start of End-of-Day
If the terminal has hardware problems and cannot finalize the function
any more
Go to another WebMaster terminal
Select
5 System Functions
6 Remove Function Lock
Click on check box "Lock Status" to remove status
Click on button "Unlock"
Retry End-of-Day again
4. Offline
Check why the terminal is offline and correct the situation
(e.g. not turned on, LAN cable pulled etc.)
5. Files Mismatch
Turn off terminal which has file mismatch,
Declare this terminal defect
Start End-of-Day again
Call NCR technician
Leave the terminal turned off until it is repaired again.
6. Datatransfer
Wait some seconds until datatransfer from terminal to POS Server is
finished.
7. Terminal is locked
The lock flag of this client is shown; e.g. the client is still in
maintenance. See example 6.1.1
During End-of-Day
If the End-of-Day was aborted manually, the End-of-Day has to be started again and will
continue where it was stopped.
2. The terminal which initialized End-of-Day has hardware problems, EoD stopped.
CoreStatus.Log Example:
2004/12/02 12:13:43 Login - #==========================
Login - # <USER-LOGIN>
Login - #
Login - # USER NUMBER : 802
Login - # USER NAME : Supervisor 2
Login - # LOGIN ID : 802
Login - # TERMINAL NUMBER : 801
Login - # POS SERVER : 915
Login - # SECRET NUMBER : 2
..
2004/12/02 12:13:45 TerminalEvaluation - TERMINALS_READY [---]
TerminalEvaluation - WEB_CLIENTS_READY [802]
TerminalEvaluation - SIGNED_IN [011,801]
TerminalEvaluation - DATATRANSFER [---]
TerminalEvaluation - OFFLINE [---]
TerminalEvaluation - FILES_MISMATCH [---]
TerminalEvaluation - DEFECTIVE [---]
TerminalEvaluation - EOD [---]
The user 802 started the EoD at Terminal 801 and only user 802 with the terminal selection
801 can continue with the End-of-Day procedure!
-----------------------------------------------------
LoginCTL
-----------------------------------------------------
Change LoginCTL.selectTerminal=1
Exit file
Save changes
Click on JREStop
2.4 Login
Login with
correct User number (in this example: 806)
Secret number
Select correct terminal (in this example: 806)
The End-of-Day procedure will continue at the step where it was interrupted.
4. End-of-Day aborted
The EoD was aborted through an incident.
The screen will show End-of-Day aborted.
The Main Menu will show the status as following:
Start End-of-Day again with same Operator number and password. The system will continue at
the next following EoD step if there is no major file or hardware problem detected.
The print icon will print all reports defined to be included in the End-of-Day.
Note:
The print of the End-of-Day reports has to be before the next End-of-Day is started.
The print can be repeated until the next End-of-Day was performed. The next day the last End-of-
Day reports can be printed with the function "Print old EoD Spoolfiles" - see 6.3.2.
In the standard (= demo version) the following reports are included in the End-of-Day reports:
This function will display the last 10 days of End-of-Day spoolfiles. The last one is always No. 1
and on top of the list. 10 days is the standard setting and can be modified in the eod.properties
ptd.duration=10.
The printing of the last End-of-Day Reports will add onother entry to the old EoD Spoolfiles and
insert it as No. 1.
The End-of-Day change at the Server will be performed, all files will be saved, the terminals will
be reset and receive the new days data. The reports are printed at the POS terminal which
started the EOD.
When the WebMaster is life again, this function is used to Re-Run the Server End-of-Day at the
WebMaster. All WebMaster files will be updated and End-of-Day reports can be printed.
A list of the last End-of-Days performed by the POS terminals and finalized through the POS
Server will be shown.
In the example above two generations are available at the POS Server, no WebMaster files
were updated.
The oldest generation will be processed first when the rerun is now started.
All generations have to be processed.
If there are unprocessed POS Server End-of-Day files, a WebMaster End-of-Day cannot be
started. The older End-of-Day files have to be processed first with a Rerun-End-of-Day.
A Re-Run EoD can be done any time during the day. The POS Server and the POS terminals
will not be included in this procedure.
Note:
A Re-Run EoD can only be started if no End-of-Day procedure was aborted. The normal End-
of-Day procedure has to be finalized first, then a Re-Run of an earlier performed Server-End-
of-Day can be started.
6.8 POS-EoD
This button is under higher authorization and has to be opened when the option for a 24 hour
store is set.
For 24 hour stores the Auto-EoD flag has be set at the POS server (srv.ini) to allow an End-
of-Day terminal by terminal.
This means, when the POS-EoD button is pressed at WebMaster, the Server will provide new
parameters and will set an EoD request for all POS terminals. As soon as a POS terminal is
signed off, it will perform it's EoD and copy the new parameters from the Server. The next
terminals will act in the same manner.
The terminals can be started again immediately. All transactions will add to the new day. Data
mirroring to the server is disabled until the System-EoD has been performed through the
WebMaster.
When all terminals have performed their End-of-Day the System End-of-Day has to be
started.