massupdate

SPID Mass Update

The optional mass update utility provides the ability to migrate subscription version, number pool block, and network data from one Service Provider ID (SPID) to another based on an input file downloaded from the NPAC. The mass update utility reads SIC-SMURF files for LRN, NPA-NXX, and NPA-NXX-X, performs the required database updates and, in the case of LRN data, forwards an appropriate Update Override GTT message to the EAGLE.

Keyword

Permission

The user must be logged in with the user name lsmsadm.

Syntax

Optional flags:

-v

Provides verbose output.

-p

Perform “pre-check” but make no database updates.

-n

Perform the mass update only for the region named by the <npacRegion> parameter. Only one NPAC region may be entered after the -n option

Parameters

<npacRegion>

The name of the region to perform the mass update for.

<filename>

The name of the SIC-SMURF file to process.

SIC-SMURF-[LRN|NPANXX|NPANXXX].OldSpid.NewSpid.DD-MM-YYYYHH24MISS

Example: SIC-SMURF-NPANXX.0001.0002.25-12-1996081122

Sample Output

One or more npacagents processes are currently running.  They must be
Stopped prior to mass spid updates by executing the following command:
/lsms stop <region>
Massupdate: exiting.

WARNING: The supman, lsman or an eagleagent process is currently running. It is recommended that all of these processes be stopped prior to mass spid updates to prevent modifications of GTT data during execution of this command.
Do you wish to continue [N]? 
Massupdate: exiting.

Using SIC-SMURF File: SIC-SMURF-LRN.1234.9876.15-03-2002121530
Performing Mass Update of SPIDs for LRN data...
Updating LRN 2223334000 from SPID 1234 to SPID 9876...
5 OverrideGtt object(s) updated in supported database
1 ServiceProvLRN object(s) updated in Southeast region
4 NumberPoolBlock object(s) updated in Southeast region
Updating LRN 2224441000 from SPID 1234 to SPID 9876...
0 OverrideGtt object(s) updated
1 ServiceProvLRN object(s) updated in Southeast region
10 NumberPoolBlock object(s) updated in Southeast region
Updating LRN 2225550000 from SPID 1234 to SPID 9876...
4 OverrideGtt object(s) updated
0 ServiceProvLRN object(s) updated in Southeast region
4 NumberPoolBlock object(s) updated in Southeast region
Updating SubscriptionVersion tables (this may take a while)...
790 SubscriptionVersion object(s) updated in Southeast region
Command stats
-------------
Lines processed: 3
Successful:      3
Failed:          0
Command complete.
$

WARNING: The supman, lsman or an eagleagent process is currently running. It is recommended that all of these processes be stopped prior to mass spid updates to prevent modifications of GTT data during execution of this command.
Do you wish to continue [N]? Y

START Mass update command: Thu Nov  8 13:41:57 EST 2007

Precheck mode: Makes NO CHANGES, but reports everything as if updating.

Executing mass update for all regions...
 {Precheck only}
Reading SIC-SMURF File: SIC-SMURF-LRN.TKLC.SP05.06-30-2004101010

Performing Mass Update of SPIDs for LRN data... {Precheck only}

Command stats {Precheck only}
-------------
Lines processed: 1
Successful:      1
Failed:          0

Mass update command complete: Thu Nov  8 13:41:57 EST 2007

For each table/field that is affected, the field that is checked for a match is listed under the appropriate SIC-SMURF filename. Under the Table/Field column, the database containing the object to be updated (for example, SupDB), the table to be updated (for example, OverrideGTT), and the field to be updated (for example, spid) are listed.

Under each SIC-SMURF file type, the field to be used for the match (for example, lrn) is listed for each Table/Field impacted by the update. For example, for LRN SIC-SMURF files, the SupDB OverrideGTT table's spid is updated if the lrn is matched.

If an Override GTT entry is modified and there is no LSMS Service Provider with the NewSpid, then one is created. If that LSMS Service Provider SPID is not a member of the GTT group for a modified Override GTT, then that membership is added by creating a GTT Group SPID table entry.

If a ServiceProvLRN, ServiceProvNPA_NXX, or ServiceProvNPA_NXX_X object is modified and there is no ServiceProvNetwork object with the NewSpid, then one is created.

LsmsServiceProvider Limit

The mass update utility creates LsmsServiceProvider objects, if needed, even if creating them exceeds the maximum number of SPIDs supported (as recorded in the MAX_SPIDS field in the DbConfig entry.) However, the fact that the limit has been exceeded is recorded in the log file and the limit remains in force otherwise.

Mass Update Log File

To record information or errors during the mass update or the precheck, the mass update utility appends to a log file named massupdate.log.MMDD, located in the $LSMS_DIR/../logs/massupdate directory. The .MMDD suffix is the month and day the massupdate excution begins. If the massupdate runs past midnight, it will keep all output from one massupdate execution in one file, so the file will not be split across days but continue in the same file it started in. The following information is written to the log file by the mass update utility:

• The path name of the mass update input file being used

• The time and date for the start and stop of utility execution

• Identifying information for all automatically created objects, whether ServiceProvNetwork or LsmsServiceProvider, including the adding of a (possibly already existing) LsmsServiceProvider to a GttGroup and noting if a newly created LsmsServiceProvider is over the MAX_SPIDS limit

• Identifying information for any LsmsServiceProvider objects that are no longer used in any OverrideGtt as a result of the mass update and therefore could be removed

• Output from the precheck

• Any kind of processing problem or error

• A summary showing the number of lines actually processed successfully for each invocation of the utility (not needed for precheck mode)

Error Codes