DOWNLOAD Sharp UP-3500 (serv.man34) Service Manual ↓ Size: 782.08 KB | Pages: 59 in PDF or view online for FREE

When the master or back-up master recovers from a breakdown, the recovery declaration operation should
be taken to inform satellites of the recovery.

1) The recovery declaration operation is done at the back-up master.

2) Each satellite stops sending updated GLU data (and clerk data*) to the back-up master

temporarily.

3) The back-up master sends the updated GLU data (and clerk data*) files to the master.

4) The back-up master informs all satellites of the master's recovery.

5) The satellites restart sending updated GLU data (and clerk data*) to the master and the IRC

system returns to the normal state.

*Only for the centralized clerk file system

The recovery declaration procedure is as follows:

Enter the PGM2 mode from the mode selection window.

Select “7 DECLARE & RECOVERY MA/BMA” from the displayed menu.

The DECLARE & RECOVERY MA/BMA window will appear.

Select “2 SYNCHRONIZE DB MA/BMA.”

3) Updated data file

Satellite

4) Master
     recovery
     information

2) Transmission stops temporarily.

Recovery declaration

  1) Recovery
      declaration
      operation

Back-up master

Master

5) Restart of updated
     data transmission  

1) The recovery declaration operation is done at the master.

2) Each satellite stops sending updated GLU data (and clerk data*) to the master temporarily.

3) The master sends the updated GLU data (and clerk data*) files to the back-up master.

4) The master informs all satellites of the back-up master's recovery.

5) The satellites restart sending updated GLU data (and clerk data*) to the back-up master and the

IRC system returns to the normal state.

*Only for the centralized clerk file system

The recovery declaration procedure is the same as “(1) When the master recovers from a breakdown.”

2) Transmission stops 
      temporarily.

3) Updated data file

Satellite

4) Back-up master 
      recovery information

Back-up master

Master

 1) Recovery declaration

5) Restart of updated data transmission

5

In case of trouble, you can forcibly clear a specific item memory causing the trouble using the manual clear
operation to restore the system. This operation should be done only when the master or system breaks
down.

With the following procedure, you can specify and clear an item memory causing trouble.

Enter the PGM2 mode from the mode selection window.

Select “4 DATA CLEAR” from the displayed menu.

The DATA CLEAR window will appear.

Referring to the list below, select an appropriate item memory to be cleared to restore the system.

Manual clearing of the clerk 

sign-on state

Manual clearing of the ‘GLU 

data in use’ state

Manual clearing of the 

GENERAL (dept. and 

transaction) data memory

Manual clearing of the hourly 

sales data memory

Manual clearing of the clerk 

sales data memory

Manual clearing of the cashier 

sales data memory

Manual clearing of the daily net 

sales data memory

Manual clearing of the T-LOG 

buffer

Manual clearing of the electronic 

journal data

M

M

M

M

M

M

M

M

M

-

-

S

S

S

S

S

S

S

Effective only for clerks who is in the 

sign-on state at the master. (*2)

This operation clears all GLU data 

that is currently in use.

Only for the clerk + cashier system.

For T-LOG polling, see page 17.

SIGN ON FLAG

GLU USED FLAG

TRANSACTION

HOURLY

CLERK

CASHIER

DAILY NET

T-LOG

E. JOURNAL

*

1

 ‘M’ denotes manual clearing functions available at the master while ‘S’ denotes manual clearing functions available at 

satellites.

*

2

 Clerk sales data for each satellite at which a clerk signs on is not collected by manual clearing of the sign-on state. 

Clerk sales data is collected only when sign-off operation is done correctly at satellites.

If a transmission job from the master to a satellite is not performed successfully, the master either
terminates the job immediately or enters command entry awaiting state depending on whether the system
retry function has been disabled or enabled. When the system retry function has been enabled, the master
awaits entry of a command and retries access depending on the commands as explained on the following
page.
System retry function is also available at satellites depending on a type of transmission error.

This function is used in the following cases:

• The master has failed to download preset or updated data to all or some of the satellites.
• The master has failed to collect sales report data from all or some of the satellites.
• The satellite has failed to download data to other machines.
• A clerk has failed to sign off at a satellite.*

Whether the system retry function is enabled or disabled when a transmission error occurs is
programmed both at the master and a satellite. (See “5. Specifying whether to enable or disable the
system retry function when a transmission error occurs” on page 41.)

*When a clerk has failed to sign off at a satellite for some reason (e.g. the master is busy), the RETRY

and ABORT commands are available but the IGNORE command is not.

The master terminates the transmission job immediately in the following two ways.
If none of the satellites have successfully transmitted data, the transmission is regarded as having
ended with an error, which is equivalent to ABORT as discussed on the following page.
If there is any satellite which has successfully transmitted data, the transmission is regarded as either
successful or unsuccessful depending on the type of transmission job. In this case, the transmission
regarded as successful and the one regarded as unsuccessful are equivalent to IGNORE and ABORT,
respectively, both of which are explained on the following page.