DescriptionMessage
A write transaction has been
opened.
begin_txn (iid 2, type write)→
rsp (iid 2, rc 0)←
Two new DNs are being added
to the existing IMSI 9195551000.
ent_sub (iid 3, imsi 9195551000, dn 9195551214, dn
9195551215, sp 9195550000)
→
The IMSI already had two DNs
rsp (iid 3, rc 0)←
(9195551212 and 9195551213)
from the previous creation
example scenario, giving it a total
of four DNs.
This command moves the
specified IMSI and its four DNs
to the SP 9195556666.
upd_sub (iid 4, imsi 9195551000, sp 9195556666)→
rsp (iid 4, rc 0)←
This command moves the
specified single DN to SP
9195550000.
upd_sub (iid 5, dn 9195551502, sp 9195550000)→
rsp (iid 5, rc 0)←
This command moves the
specified standalone DN to be
upd_sub (iid 6, dn 9195551501, imsi 9195552001)→
rsp (iid 6, rc 0)←
associated with the specified
IMSI. The DN will now get its SP
from the IMSI.
The write transaction has ended.
The updates will be written to the
database.
end_txn (iid 7)→
rsp (iid 7, rc 0, data (dblevel 2))←
The client is done and has
disconnected.
disconnect (iid 8)→
rsp (iid 8, rc 0)←
This example shows how the upd_sub command works with respect to the V-Flex feature. The
following actions are shown in the example:
• Create new DN with a VMS
• Create new DN on SP/RN
• Move an existing DN to a new SP/RN
• This illustrates how update works to replace SP/RN when SP/RN association already existed.
• Add a VMS association to an existing DN
144
910-6022-001 Revision A, March 2011
PDBI Sample SessionsProvisioning Database Interface Manual
To Next Page
Loading...
