When the keyword PREFIX is specified all record matching is performed using the data entered as a partial key. For example:
TSS LIST(SDT) CALENDAR(WEEK) PREFIX
CALENDAR entries that would satisfy this list command are: WEEKEND, WEEKDAYS, etc.
Examples: List SDT record elements with PREFIX
This example lists the SDT table using the prefix option:
TSS LIST(SDT) CALENDAR(xxxxxxxx) PREFIX
TSS LIST(SDT) CALENDAR(xxxxxxxx) YEAR(yyyy) PREFIX
TSS LIST(SDT) MAPREC(xxxxxxxx) PREFIX
TSS LIST(SDT) MASKREC(xxxxxxxx) PREFIX
TSS LIST(SDT) RECORD(xxxxxxxx) PREFIX
TSS LIST(SDT) SELECT(xxxxxxxx) PREFIX
TSS LIST(SDT) TIMEREC(xxxxxxxx) PREFIX
1 to 8 characters
Must be 4 numeric characters
In a shared security file environment, all modifications to any SDT record type and data field made in the local system are immediately available to the TSS LIST command if entered from the same local system.
If the SDT modifications are made on a local system and the TSS LIST is attempted from a remote system, it is possible that some SDT records will not reflect the current changes as they are listed from internal tables not updated with the current data. The SDT record types and data fields that may experience this effect include:
For immediate access to the current TSS LIST record data for any of the included SDT record types on a remote system, enter the TSS MODIFY SYNCH command to refresh the required tables with current data from the security file.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|