XMA: Safeguard Mover Abends After Pathway Reset and Daylight Savings has ended

XMA: Safeguard Mover Abends After Pathway Reset and Daylight Savings has ended

Use the following steps in order to resolve this condition:
 
You will need the last record processed by the Safeguard mover.
  1. TACL> VOLUME $<XMA Database Volume/Subvolume>
  2. TACL> SQLCI
  3. >> SELECT LASTRECORDGMTTSTMP FROM SFGST BROWSE ACCESS;
SQL Conversational Interface - T9191H01^ACR - (28MAY12)
(C) 1987 COMPAQ (C) 2012 Hewlett Packard Development Company, L.P.
 >>select lastrecordgmttstmp from sfgst browse access;
 
LASTRECORDGMTTSTMP
2012-07-26:19:29:42.148346
2012-08-07:00:03:48.573710
2012-08-07:21:08:19.171460
2012-08-13:09:02:02.874492
2012-08-23:18:14:51.216681
2012-08-26:06:38:06.865449
2012-09-07:14:30:38.330562
2012-09-18:13:09:51.611657
2012-09-19:18:18:20.641066
2012-09-19:20:25:05.099852
2012-09-19:20:37:28.709716
2012-09-19:22:42:52.770234
2012-09-19:22:49:19.364039
2012-09-19:23:30:15.788781
2012-09-20:15:53:53.790853
2012-09-20:18:29:31.723788
2012-09-28:13:00:40.771679
--- 17 row(s) selected.
  1. Make note of the LAST TIMESTAMP from the output
  2. Enter the following 2 SQL statements. Substitute your Safeguard mover's name for the SFG-node-01 
DELETE FROM SFGAUX WHERE SERVERCLASSNAME = "SFG-node-01";
DELETE FROM SFGST WHERE SERVERCLASSNAME = "SFG-node-01";
  1. Type: EXIT to exit SQLCI
  2. Start the mover substituting the TIMESTAMP found from step 3.
    1. TACL> VOLUME $VOL.XYGATEMA
    2. TACL> RUN XMA INSTALL
    3. TACL> XMA_MANAGER
    4. Select 2: MOVERS
    5. Select 5: START
    6. Enter S (or 5 in V2.15 and higher) for the Safeguard mover serverclass
Example (v 2.10 and older) :
Enter the serverclass type <X(ygate), M(easure), E(ms), S(afeguard), B(ase24) or H(lr)> ->S

Example (v 2.15 and greater) :
Serverclass Types

1:  XYGATE
2:  Base24
3:  Measure
4:  EMS
5:  Safeguard
6:  HLR
7:  Other

<CTRL-Y>:  Exit

Please enter the serverclass type -> 5
  1. Enter the name of the serverclass- > SFG-X-01
  2. Enter the timestamp for where in the database you want this mover to start (Found from step 3): 2012-09-28:13:00:40.771679
Please enter the serverclass name <S>->SFG-X-01
Checking SFG-X-01 status ...
Running $system.system.sqlci /inv commandin, out $VOL.XMADAT.zz000000/
to get the last processed record's timestamp
 
To start data collection from the beginning of existing audits, enter -1.
To start data collection from a certain number of days ago, enter a number
greater than 1.
To start data collection from a specific date onwards, enter a date in the
format yyyy-mm-dd [hh:mn[:ss]]
 
Begin gathering data from midnight today or enter the desired date: <2012-11-20:
00:00:00.000000>->2012-09-28:13:00:40.77167
Data collection start date will be set to 2012-09-28:13:00:40.000000.
Updating database configuration for SFG-X-01 ...
starting mover SFG-X-01 ...
Command completed successfully
Press Return to continue ...
 
If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.

    • Related Articles

    • XMA: Newly added EPS Mover abends and will not start

      If a newly added EPS mover is abending and will not start steps should be taken to ensure both the UALOGD and UALOGD0 can be accessed by Merged Audit. Please check both files have appropriate guardian security and that there is no safeguard ACL ...

    • XMA: Measure Mover Keeps Abending

      Is XYPRO SecurityOne installed? The Measure mover is not designed to collect system performance metrics. It is designed to only capture process information for the XYGATE SecurityOne WHO Resolver. The MEASURE mover collects information regarding ...

    • XMA: Saveabend files are not being created by mover abends

      1. Does the security of the XYGATEMA (XMA) installation disk volume or subvolume allow CREATE access to the XMA installation owner? Check for any Safeguard volume or subvolume ACLs or XYGATEOS rules that prevent WRITE or CREATE access for the XMA ...

    • XMA: Safeguard mover is opening $ZNET.#ZSPI on remote nodes

      This is normal behavior. There is a field on some Safeguard records indicating the terminal id and some of those records do not include a TCP/IP address. In those cases, the Safeguard mover attempts to find the TCP/IP address associated with the ...

    • XSR: Safeguard mover abends with PROCESS_CREATE_ error on XYGATESR.

      FIX: Restart the CMON process, and start the Safeguard mover. If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.