SBMJOB ... CPYENVVAR(*NO)

[Guest.Visitor]

We've just upgraded to V3R2.&#160 A new keyword was added into SBMJOB command: Copy environment variables . . . CPYENVVAR *NO(default). What type of enviromet variables it can copy ? The F1=Help doesn't have enough explanation. Thanks in advance, http://www2.cybernex.net/~irash>Ira

[Guest.Visitor]

On Tuesday, May 20, 1997, 03:57 PM, Ira Shapiro wrote: We've just upgraded to V3R2.* A new keyword was added into SBMJOB command: Copy environment variables . . . CPYENVVAR *NO(default). What type of enviromet variables it can copy ? The F1=Help doesn't have enough explanation. Thanks in advance, http://www2.cybernex.net/~irash>Ira Ira, I did an extended search for "environment & variables" and got quite a number of hits. But here is what I found in the OS/400 System API Programming Book. ------------------------------------------------------------------- 8.25.1 Environment Variable APIs Environment variables are character strings of the form name=value that are stored in an environment space outside of the program. The strings are stored in a temporary space associated with the job. Environment variables can be set using the putenv() or Qp0zPutEnv() function. They can be retrieved using the getenv() or Qp0zGetEnv() function. The putenv() and getenv() functions are designed to meet the X/Open** single UNIX specification (formerly Spec 1170). The Qp0zPutEnv() and Qp0zGetEnv() functions are AS/400 extensions to the industry-standard APIs. They provide the additional capability to store or retrieve a coded character set identifier (CCSID) associated with the string. After environment variables are set, they exist for the duration of the job. There is no way to remove an environment variable. However, the value can be set to NULL by using a subsequent call to putenv() or Qp0zPutEnv() and specifying a value of NULL. The OS/400 support for environment variables does differ from the usual behavior of environment variables on UNIX systems: There is no default set of environment variables provided when a job starts. On the AS/400, the environ array, which points to the environment variable strings, is NULL (not initialized) until environment variables are associated with the job. On a UNIX system, the exec() function creates a new process and extends the environment variables of the original process to the new process. Although the AS/400 has no exec() function, environment variables are extended to a new job created using the Submit Job (SBMJOB) command, provided the first job has environment variables. ---------------------------------------------------------------------- Translation? My guess is that it is an emulation of PC style variables (You know, SET TEMP=C:TEMP). BR

[Guest.Visitor]

this parm might be for compatibility on down the line infuture operating systems.... bob hamilton DEEP BLUE won only 2 of 6 games which won't evenget you on the CUBS or JETS.