DescriptionMessage
rsp (iid 8, rc 0)←
9195553000. DN 9195551600 is
now on GRN 9196660000 (NE
Query Only option) and SP
9195551100 (G-Flex).
The write transaction has ended.
The updates will be written to the
database.
end_txn (iid 9)→
rsp (iid 9, rc 0, data (dblevel 2))←
The client is done and has
disconnected.
disconnect (iid 10)→
rsp (iid 10`, rc 0)←
This example shows how the upd_sub command works with respect to G-Flex and V-Flex feature
interoperability. The following actions are shown in the example:
• Create new multi-DN IMSI on SP
• Move DN from IMSI and make it a standalone DN on a VMS
• Move DN from IMSI and make it a standalone DN on a VMS and the same SP as before
• Move multi-DN IMSI to a new SP
• Move the standalone DNs that were on the original subscription onto the new SP
• Update DN with ASD
• Remove ASD from a DN
Note: All VMSs, GRNs, & SPs in the following example are assumed to be provisioned prior to this
example
Table 30: Update Subscription Data Example 3
DescriptionMessage
A PDBI connection has been
established to the Active PDBA.
connect (iid 1, version 1.0)→
rsp (iid 1, rc 0, data (connectId 3, side active))←
A write transaction has been
opened.
begin_txn (iid 2, type write)→
rsp (iid 2, rc 0)←
The IMSI created with 5 DNs. The
subscription is on SP 9195551100.
ent_sub(iid 3, imsi 9195555000, dn 9195551310, dn
9195551311, dn 9195551312, dn 9195551313, dn 9195551314,
sp 9195551100)
→
146
910-6022-001 Revision A, March 2011
PDBI Sample SessionsProvisioning Database Interface Manual