![]() Then (2) MIGRATE on the target to change the encoding and data representation. It's a little complicated but we recommend a two-step process where you (1) COPY with the CVP engine on the source environment to avoid CEDA. We like PROC MIGRATE better than PROC COPY for migration, so we came up with a workaround. This works fine with PROC COPY, but CVP is not currently supported by PROC MIGRATE. There is a tricky scenario that tends to affect customers with DBCS data - If you are changing to a different character encoding that uses more bytes to represent the characters, you might need to use the CVP engine as part of the copy or migration process, to avoid truncation. PROC MIGRATE retains alternate collating sequence, compression, created and modified datetimes, deleted observations, encryption, extended attributes, indexes, integrity constraints, and passwords. See Cross-Environment Data Access in SAS Programmer’s Guide: Essentials. This Read-Only access is automatic and transparent, but you must be aware of the restrictions. Alternatively, if you have direct access to the source library through NFS, then you might be able to use CEDA instead of migrating.If you have direct access to the source library through NFS, and if incompatible catalogs are not present, then you can migrate without using a SAS/CONNECT or SAS/SHARE server. SAS/SECURE Java Component 9.3M1 Issue(s) Addressed: Introduced: 47011: The SAS/SECURE Java component generates a new public key for each connection instance: H83001: z/OS: Released: Octo: Documentation: H83001os.html : Download: H83001pt.For more information about CEDA, see Cross-Environment Data Access in SAS Programmer’s Guide: Essentials. In general, CEDA is invoked when you migrate to an incompatible operating environment. Processing would invoke CEDA in the target session.You are required to use a server if both of the following two conditions are met:.You can use a server to migrate across machines when you do not have direct access.Here are two reasons to use a SAS/CONNECT or SAS/SHARE server:.The SIGNOFF command ends the connection to the server. PROC MIGRATE migrates the library members from the source library to the target library. This LIBNAME statement assigns the target library to an existing location where the migrated library is to be stored. The SERVER= argument specifies the myserver macro variable and the port number. This LIBNAME statement assigns the source library to the location of the library that is to be migrated. This statement specifies to prompt for the user ID and password, but you could include them here. Change the number in the statement to your server’s port number. The SIGNON statement instructs the spawner to start a session on the SAS/CONNECT server that is named in the myserver macro variable. Use this variable to specify the name of your remote SAS/CONNECT server. The %LET statement creates the myserver macro variable. The COMAMID= option specifies to use TCP/IP as the communications access method for connecting to the SAS/CONNECT server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |