defncopy

Copies definitions for specified views, rules, defaults, triggers, or procedures from a database to an operating-system file or from an operating-system file to a database.

The utility is located in:

(UNIX) $SYBASE/$SYBASE_OCS/bin.
(Windows) %SYBASE%\%SYBASE_OCS%\bin, as defncopy.exe.

Syntax

defncopy
	[-X]
	[-a display_charset]
	[-I interfaces_file]
	[-J [client_charset]]
	[-K keytab_file]
	[-P password]
	[-R remote_server_principal]
	[-S [server_name]]
	[-U username]
	[-V security_options]
	[-Z security_mechanism]
	[-z language]
	{ in file_name database_name | 
		out file_name database_name [owner.]object_name
	 [[owner.]object_name...] }

defncopy -v

Parameters

-a display_charset – runs defncopy from a terminal whose character set differs from that of the machine on which defncopy is running. Use -a in conjunction with -J to specify the character set translation file (.xlt file) required for the conversion. Use -a without -J only if the client character set is the same as the default character set.
Note: The ascii_7 character set is compatible with all character sets. If either the SAP ASE character set or the client character set is set to ascii_7, any 7-bit ASCII character can pass unaltered between client and server. Other characters produce conversion errors. See the System Administration Guide for more information on character set conversion.
-I interfaces_file – specifies the name and location of the interfaces file to search when connecting to the SAP ASE server. If you do not specify -I, defncopy looks for a file named interfaces in the directory specified by the SYBASE environment variable in UNIX platforms, and sql.ini in the ini subdirectory for your Sybase release directory in Windows.
-J client_charset – specifies the character set to use on the client. A filter converts input between client_charset and the SAP ASE character set.
-J client_charset requests that the SAP ASE server convert to and from client_charset, the client’s character set.

-J with no argument sets character set conversion to NULL. No conversion takes place. Use this if the client and server are using the same character set.

Omitting -J sets the character set to a default for the platform. The default may not be the character set that the client is using. For more information about character sets and their associated flags, see the System Administration Guide and configuration guide for your platform.
-K keytab_file – specifies the path to the keytab file used for authentication in DCE.
-P password – specifies your password. If you do not specify -P, defncopy prompts for your password.
-R remote_server_principal – specifies the principal name for the server. By default, a server’s principal name matches the server’s network name (which is specified with the -S parameter or the DSQUERY environment variable). Use the -R parameter when the server’s principal name and network name are not the same.
-S server_name – specifies the name of the SAP ASE server to which to connect. If you specify -S with no argument, defncopy looks for a server named SYBASE. If you do not specify -S, defncopy uses the server specified by your DSQUERY environment variable.
-U username – specifies a login name. Login names are case sensitive. If you do not specify username, defncopy uses the current user’s operating system login name.
-v – displays the version and copyright message of defncopy and returns to the operating system.
-V security_options – specifies network-based user authentication. With this option, the user must log in to the network’s security system before running the utility. In this case, users must supply their network user name with the -U option; any password supplied with the -P option is ignored.
-V can be followed by a security_options string of key-letter options to enable additional security services. These key letters are:
- c – Enable data confidentiality service
- i – Enable data integrity service
- m – Enable mutual authentication for connection establishment
- o – Enable data origin stamping service
- r – Enable data replay detection
- q – Enable out-of-sequence detection
-X – initiates the login with client-side password encryption in this connection to the server. defncopy (the client) specifies to the server that password encryption is desired. The server sends back an encryption key, which defncopy uses to encrypt your password, and the server uses to authenticate your password when it arrives.
If defncopy crashes, the system creates a core file which contains your password. If you did not use the encryption option, the password appears in plain text in the file. If you used the encryption option, your password is not readable.
-z language – is the official name of an alternate language that the server uses to display defncopy prompts and messages. Without the -z flag, defncopy uses the server’s default language.
Add languages to an SAP ASE at installation, or afterwards with the utility langinstall (langinst in Windows) or the stored procedure sp_addlanguage.
-Z security_mechanism – specifies the name of a security mechanism to use on the connection.
Security mechanism names are defined in the $SYBASE/install/libtcl.cfg configuration file. If no security_mechanism name is supplied, the default mechanism is used. See the description of the libtcl.cfg file in the Open Client and Open Server Configuration Guide.
database_name – specifies the name of the database to copy the definitions from or to.
file_name – specifies the name of the operating system file destination or source for the definition copy. The copy out overwrites any existing file.
in | out – specifies the direction of definition copy.
object_name – specifies names of database object for defncopy to copy out. Do not use objectname when copying definitions in.
owner – is optional if you or the database owner own the table being copied. If you do not specify an owner, defncopy first looks for a table of that name that you own, and then looks for one owned by the database owner. If another user owns the table, specify the owner name or the command fails.

Examples

Files – Copies definitions from the file new_proc into the database stagedb on server MERCURY. The connection with MERCURY is established with a user of name “sa” and a NULL password:
```
defncopy -Usa -P -SMERCURY in new_proc stagedb
```
Objects – Copies definitions for objects sp_calccomp and sp_vacation from the employees database on the SYBASE server to the file dc.out. Messages and prompts display in french. The user is prompted for a password:
```
defncopy -S -z french out dc.out employees sp_calccomp sp_vacation
```

Usage

Use this syntax for defncopy_r if you are using threaded drivers.
Use this syntax for defncopy you are using threaded drivers in the IBM platform.
Set the SYBASE environment variable to the location of the current version of SAP ASE before using defncopy.
Invoke the defncopy program directly from the operating system. defncopy provides a noninteractive way to copy out definitions (create statements) for views, rules, defaults, triggers, or procedures from a database to an operating system file. Alternatively, it copies in all the definitions from a specified file.
The in filename or out filename and the database name are required and must be stated unambiguously. For copying out, use file names that reflect both the object’s name and its owner.
defncopy ends each definition that it copies out with the comment:
```
/* ### DEFNCOPY: END OF DEFINITION */
```
Definitions created as text must end with this comment so that defncopy can copy them in successfully.
Enclose values specified to defncopy in quotation marks, if they contain characters that could be significant to the shell.

Warning! Long comments of more than 100 characters that are placed before a create statement may cause defncopy to fail.
SDK binaries like defncopy use the same names in both 32-bit and 64-bit products. Installing SAP ASE, the SDK, or Open Server 64-bit products with other Sybase 32-bit products overwrites the 32-bit binaries. Starting with SAP ASE 15.0.2 and SDK/Open Server 15.0 ESD #9, the 64-bit binaries are replaced with 32-bit binaries on all 64-bit UNIX platforms. Since 32-bit binaries are included in the 64-bit EBF, the -v option of defncopy is no longer a valid way to check the EBF number for 64-bit products. Instead, use the UNIX strings and grep commands to confirm the EBF numbers for both Open Client and Open Server.

For example, to find the string containing the EBF number in the libsybct64.a library, enter:

strings -a libsybct64.a | grep Sybase

This returns a string similar to:
```
Sybase Client-Library/15.5/P/DRV.15.5.0/SPARC/Solaris
8/BUILD1550-001/64bit/OPT/Mon Aug 10 23:04:17 2009
```
To find the string containing the EBF number in the libsybsrv64.a library, enter:

strings -a libsybsrv64.a | grep Sybase

This returns a string similar to:
```
Sybase Server-Library/15.5/P/DRV.15.5.0/SPARC/Solaris
8/BUILD1550-001/64bit/OPT/Mon Aug 10 23:06:27 2009
```

Permissions

You must have select permission on the sysobjects and syscomments tables to copy out definitions; you do not need permission on the object itself.
You may not have select permission on the text column of the syscomments table if the system security officer has reset the allow select on syscomments.text column parameter with the system procedure sp_configure. This reset restricts select permission to the object owner and the system administrator. This restriction is required in order to run SAP ASE in the evaluated configuration , as described in the installation and configuration documentation for your platform. In this case, the object owner or a system administrator must execute defncopy to copy out definitions.

Note: If the text has been encrypted, it may be hidden from you even if you have all the required permissions. See “Verifying and Encrypting Source Text” in the Transact-SQL User’s Guide.
You must have the appropriate create permission for the type of object you are copying in. Objects copied in belong to the copier. A system administrator copying in definitions on behalf of a user must log in as that user to give the user proper access to the reconstructed database objects.

Tables used

syscomments, sysobjects