- The VSE operating environment is no longer supported. The MVS
operating environment continues to be supported; however, it is now referred
to as the OS/390 environment.
- The windowing interface is not supported. You can no longer create
and edit access descriptors and view descriptors by using the Access Descriptor
and View Descriptor windows. You must use the line-mode interface.
Four database-definition statements have been added to support line-mode
editing of descriptor files: UPDATE, DELETE, INSERT, and REPLACE. Together
with some existing grammar, these statements provide the basis for IMS data
- Enhanced naming conventions and support enable you to use 32-byte
names for SAS data set and variable names. You can also use mixed-case names
and names that were nonstandard in Version 6. Both the interface view engine
and the DATA step interface take advantage of the new naming flexibility.
- The interface view engine has been modified to automatically generate
names of SAS variables instead of requiring you to assign names with the SASNAME=
argument. The new SAS names will be generated from those specified in the
ITEM database-definition statement. The following guidelines apply:
The following statements have also changed as result of
the new naming scheme.
- Implementation of the naming conventions must be all or nothing.
You cannot mix the Version 6 naming conventions with later naming conventions.
- Short or long name usage on access and view descriptors are independent
of each other. That is, an access descriptor can be specified with a short
name while a view descriptor that is derived from it can use a long name.
Similarly, an access descriptor that is specified with a long name can be
used to generate a view descriptor that has a short name.
- The influence of the ASSIGN and UNIQUE statements is the same
in Versions 7 and 8 as it was in Version 6. That is, if AN=Y, the names generated
for the access descriptor will be used in all view descriptors, regardless
of whether short or long names are used. If UN=Y, unique names will be generated
- The LIST statement no longer generates a "SAS Name" column.
- The RENAME statement changes the ITEM name instead of the
8-character SAS name, unless you are running in Version 6 mode.
- For interface view engine customers who need Version 6 compatibility
and more flexible variable naming options, Versions 7 and 8 provide the SAS
system option VALIDVARNAME= . The VALIDVARNAME= option lets users control
what type of variable names will be allowed in a SAS session by converting
variable names that do not conform to the necessary format. The SAS system
option has four possible values:
||for Version 6-style, eight-byte "short"
||(the default) for mixed-case, "long"
names of up to 32 bytes|
||for uppercase names of up to 32 bytes|
||for names of up to 32 characters of any type. ANY
is useful for IMS ITEM names that contain non-standard characters.|
The V6 option offers comparable functionality to the Version 6 interface
view engine. When any of the other VALIDVARNAME values are specified, the
interface view engine generates long names based on the ITEM database-definition
statement for any nonconforming names. Under these rules, Version 6 programs
will run, but WHERE processing is not available. When VALIDVARNAME=V6, any
SAS variable names longer than 8-bytes are truncated.
- Use care when choosing a VALIDVARNAME format: when
a conversion is made, the original variables' names are not stored. For more
information on the VALIDVARNAME SAS System option, see SAS Language Reference: Dictionary.
- The KEY argument of the GROUP and ITEM database
has another value. The acceptable values are:
When KEY=U is used, retrieval calls to IMS will be reduced because
the IMS interface view engine knows there is only one segment in the database
for this key.
||the field is not a key sequence field|
||the field is used as a key sequence field in the
||the field has been specified as a unique key sequence
field in the IMS DBD|
Copyright 1999 by SAS Institute Inc., Cary, NC, USA. All rights reserved.