X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=vms%2Fperlvms.pod;h=b8993d818d1c1635af183ee0e716b488f88275f6;hb=2c864a0811fbe4cad763045a119f93a241340a2f;hp=bf2b27d235619732b82371fb3f2714267f2c10ce;hpb=6ac6a52b90121db9304782c76ae9243ce4205369;p=p5sagit%2Fp5-mst-13.2.git diff --git a/vms/perlvms.pod b/vms/perlvms.pod index bf2b27d..b8993d8 100644 --- a/vms/perlvms.pod +++ b/vms/perlvms.pod @@ -182,114 +182,114 @@ translates to the full file specification of the shareable image. =head2 Syntax -We have tried to make Perl aware of both VMS-style and Unix- -style file specifications wherever possible. You may use -either style, or both, on the command line and in scripts, -but you may not combine the two styles within a single file -specification. VMS Perl interprets Unix pathnames in much -the same way as the CRTL (I the first component of -an absolute path is read as the device name for the -VMS file specification). There are a set of functions -provided in the C package for explicit -interconversion between VMS and Unix syntax; its -documentation provides more details. - -Perl is now in the process of evolving to follow the setting of -the DECC$* feature logical names in the interpretation of UNIX pathnames. -This is still a work in progress. - -For handling extended characters, and case sensitivity, as long as -DECC$POSIX_COMPLIANT_PATHNAMES, DECC$FILENAME_UNIX_REPORT, and -DECC$FILENAME_UNIX_ONLY are not set, then the older Perl behavior -for conversions of file specifications from UNIX to VMS is followed, -except that VMS paths with concealed rooted logical names are now -translated correctly to UNIX paths. - -With those features set, then new routines may handle the translation, -because some of the rules are different. The presence of ./.../ -in a UNIX path is no longer translated to the VMS [...]. It will -translate to [.^.^.^.]. To be compatible with what MakeMaker expects, -if a VMS path can not be translated to a UNIX path when unixify -is called, it is passed through unchanged. So unixify("[...]") will -return "[...]". - -The handling of extended characters will also be better with the -newer translation routines. But more work is needed to fully support -extended file syntax names. In particular, at this writing Pathtools -can not deal with directories containing some extended characters. - -There are several ambiguous cases where a conversion routine can not -determine if an input filename is in UNIX format or in VMS format, -since now both VMS UNIX file specifications can have characters in -them that could be mistaken for syntax delimiters of the other type. -So some pathnames simply can not be used in a mode that allows either -type of pathname to be present. - -Perl will tend to assume that an ambiguous filename is in UNIX format. - -Allowing "." as a version delimiter is simply incompatible with -determining if a pathname is already VMS format or UNIX with the -extended file syntax. There is no way to know if "perl-5.8.6" that -TAR produces is a UNIX "perl-5.8.6" or a VMS "perl-5.8;6" when -passing it to unixify() or vmsify(). - -The DECC$FILENAME_UNIX_REPORT or the DECC$FILENAME_UNIX_ONLY logical -names control how Perl interprets filenames. - -The DECC$FILENAME_UNIX_ONLY setting has not been tested at this time. -Perl uses traditional OpenVMS file specifications internally and in -the test harness, so this mode may have limited use, or require more -changes to make usable. - -Everything about DECC$FILENAME_UNIX_REPORT should be assumed to apply -to DECC$FILENAME_UNIX_ONLY mode. The DECC$FILENAME_UNIX_ONLY differs -in that it expects all filenames passed to the C runtime to be already -in UNIX format. - -Again, currently most of the core Perl modules have not yet been updated -to understand that VMS is not as limited as it use to be. Fixing that -is a work in progress. - -The logical name DECC$POSIX_COMPLIANT_PATHNAMES is new with the -RMS Symbolic Link SDK. This version of Perl does not support it being set. - - -Filenames are case-insensitive on VAX, and on ODS-2 formatted -volumes on ALPHA and I64. - -On ODS-5 volumes filenames are case preserved and on newer -versions of OpenVMS can be optionally case sensitive. - -On ALPHA and I64, Perl is in the process of being changed to follow the -process case sensitivity setting to report if the file system is case -sensitive. - -Perl programs should not assume that VMS is case blind, or that -filenames will be in lowercase. - -Programs should use the File::Spec:case_tolerant setting to determine -the state, and not the $^O setting. - -For consistency, when the above feature is clear and when not -otherwise overridden by DECC feature logical names, most Perl routines -return file specifications using lower case letters only, -regardless of the case used in the arguments passed to them. -(This is true only when running under VMS; Perl respects the -case-sensitivity of OSs like Unix.) - -We've tried to minimize the dependence of Perl library -modules on Unix syntax, but you may find that some of these, -as well as some scripts written for Unix systems, will -require that you use Unix syntax, since they will assume that -'/' is the directory separator, I If you find instances -of this in the Perl distribution itself, please let us know, -so we can try to work around them. +We have tried to make Perl aware of both VMS-style and Unix-style file +specifications wherever possible. You may use either style, or both, +on the command line and in scripts, but you may not combine the two +styles within a single file specification. VMS Perl interprets Unix +pathnames in much the same way as the CRTL (I the first component +of an absolute path is read as the device name for the VMS file +specification). There are a set of functions provided in the +C package for explicit interconversion between VMS and +Unix syntax; its documentation provides more details. + +We've tried to minimize the dependence of Perl library +modules on Unix syntax, but you may find that some of these, +as well as some scripts written for Unix systems, will +require that you use Unix syntax, since they will assume that +'/' is the directory separator, I If you find instances +of this in the Perl distribution itself, please let us know, +so we can try to work around them. Also when working on Perl programs on VMS, if you need a syntax -in a specific operating system format, then you need to either +in a specific operating system format, then you need either to check the appropriate DECC$ feature logical, or call a conversion routine to force it to that format. +The feature logical name DECC$FILENAME_UNIX_REPORT modifies traditional +Perl behavior in the conversion of file specifications from UNIX to VMS +format in order to follow the extended character handling rules now +expected by the CRTL. Specifically, when this feature is in effect, the +C<./.../> in a UNIX path is now translated to C<[.^.^.^.]> instead of +the traditional VMS C<[...]>. To be compatible with what MakeMaker +expects, if a VMS path cannot be translated to a UNIX path, it is +passed through unchanged, so C will return C<[...]>. + +The handling of extended characters is largely complete in the +VMS-specific C infrastructure of Perl, but more work is still needed to +fully support extended syntax filenames in several core modules. In +particular, at this writing PathTools has only partial support for +directories containing some extended characters. + +There are several ambiguous cases where a conversion routine cannot +determine whether an input filename is in UNIX format or in VMS format, +since now both VMS and UNIX file specifications may have characters in +them that could be mistaken for syntax delimiters of the other type. So +some pathnames simply cannot be used in a mode that allows either type +of pathname to be present. Perl will tend to assume that an ambiguous +filename is in UNIX format. + +Allowing "." as a version delimiter is simply incompatible with +determining whether a pathname is in VMS format or in UNIX format with +extended file syntax. There is no way to know whether "perl-5.8.6" is a +UNIX "perl-5.8.6" or a VMS "perl-5.8;6" when passing it to unixify() or +vmsify(). + +The DECC$FILENAME_UNIX_REPORT logical name controls how Perl interprets +filenames to the extent that Perl uses the CRTL internally for many +purposes, and attempts to follow CRTL conventions for reporting +filenames. The DECC$FILENAME_UNIX_ONLY feature differs in that it +expects all filenames passed to the C run-time to be already in UNIX +format. This feature is not yet supported in Perl since Perl uses +traditional OpenVMS file specifications internally and in the test +harness, and it is not yet clear whether this mode will be useful or +useable. The feature logical name DECC$POSIX_COMPLIANT_PATHNAMES is new +with the RMS Symbolic Link SDK and included with OpenVMS v8.3, but is +not yet supported in Perl. + +=head2 Filename Case + +Perl follows VMS defaults and override settings in preserving (or not +preserving) filename case. Case is not preserved on ODS-2 formatted +volumes on any architecture. On ODS-5 volumes, filenames may be case +preserved depending on process and feature settings. Perl now honors +DECC$EFS_CASE_PRESERVE and DECC$ARGV_PARSE_STYLE on those systems where +the CRTL supports these features. When these features are not enabled +or the CRTL does not support them, Perl follows the traditional CRTL +behavior of downcasing command-line arguments and returning file +specifications in lower case only. + +I It is very easy to get tripped up using a mixture of other +programs, external utilities, and Perl scripts that are in varying +states of being able to handle case preservation. For example, a file +created by an older version of an archive utility or a build utility +such as MMK or MMS may generate a filename in all upper case even on an +ODS-5 volume. If this filename is later retrieved by a Perl script or +module in a case preserving environment, that upper case name may not +match the mixed-case or lower-case expections of the Perl code. Your +best bet is to follow an all-or-nothing approach to case preservation: +either don't use it at all, or make sure your entire toolchain and +application environment support and use it. + +OpenVMS Alpha v7.3-1 and later and all version of OpenVMS I64 support +case sensitivity as a process setting (see C). Perl does not currently suppport case +sensitivity on VMS, but it may in the future, so Perl programs should +use the Ccase_tolerant> method to determine the state, and +not the C<$^O> variable. + +=head2 Symbolic Links + +When built on an ODS-5 volume with symbolic links enabled, Perl by +default supports symbolic links when the requisite support is available +in the filesystem and CRTL (generally 64-bit OpenVMS v8.3 and later). +There are a number of limitations and caveats to be aware of when +working with symbolic links on VMS. Most notably, the target of a valid +symbolic link must be expressed as a UNIX-style path and it must exist +on a volume visible from your POSIX root (see the C command +in DCL help). For further details on symbolic link capabilities and +requirements, see chapter 12 of the CRTL manual that ships with OpenVMS +v8.3 or later. + =head2 Wildcard expansion File specifications containing wildcards are allowed both on @@ -367,6 +367,63 @@ The PERL5LIB and PERLLIB logical names work as documented in L, except that the element separator is '|' instead of ':'. The directory specifications may use either VMS or Unix syntax. +=head1 The Perl Forked Debugger + +The Perl forked debugger places the debugger commands and output in a +separate X-11 terminal window so that commands and output from multiple +processes are not mixed together. + +Perl on VMS supports an emulation of the forked debugger when Perl is +run on a VMS system that has X11 support installed. + +To use the forked debugger, you need to have the default display set to an +X-11 Server and some environment variables set that Unix expects. + +The forked debugger requires the environment variable C to be C, +and the environment variable C to exist. C must be in +lower case. + + $define TERM "xterm" + + $define DISPLAY "hostname:0.0" + +Currently the value of C is ignored. It is recommended that it be set +to be the hostname of the display, the server and screen in UNIX notation. In +the future the value of DISPLAY may be honored by Perl instead of using the +default display. + +It may be helpful to always use the forked debugger so that script I/O is +separated from debugger I/O. You can force the debugger to be forked by +assigning a value to the logical name that is not a process +identification number. + + $define PERLDB_PIDS XXXX + + +=head1 PERL_VMS_EXCEPTION_DEBUG + +The PERL_VMS_EXCEPTION_DEBUG being defined as "ENABLE" will cause the VMS +debugger to be invoked if a fatal exception that is not otherwise +handled is raised. The purpose of this is to allow debugging of +internal Perl problems that would cause such a condition. + +This allows the programmer to look at the execution stack and variables to +find out the cause of the exception. As the debugger is being invoked as +the Perl interpreter is about to do a fatal exit, continuing the execution +in debug mode is usally not practical. + +Starting Perl in the VMS debugger may change the program execution +profile in a way that such problems are not reproduced. + +The C function can be used to test this functionality from within +a program. + +In typical VMS style, only the first letter of the value of this logical +name is actually checked in a case insensitive mode, and it is considered +enabled if it is the value "T","1" or "E". + +This logical name must be defined before Perl is started. + =head1 Command line =head2 I/O redirection and backgrounding @@ -460,20 +517,20 @@ Perl functions were implemented in the VMS port of Perl file tests*, abs, alarm, atan, backticks*, binmode*, bless, caller, chdir, chmod, chown, chomp, chop, chr, - close, closedir, cos, crypt*, defined, delete, - die, do, dump*, each, endpwent, eof, eval, exec*, - exists, exit, exp, fileno, getc, getlogin, getppid, + close, closedir, cos, crypt*, defined, delete, die, do, dump*, + each, endgrent, endpwent, eof, eval, exec*, exists, exit, exp, + fileno, flock getc, getgrent*, getgrgid*, getgrnam, getlogin, getppid, getpwent*, getpwnam*, getpwuid*, glob, gmtime*, goto, - grep, hex, import, index, int, join, keys, kill*, - last, lc, lcfirst, length, local, localtime, log, m//, + grep, hex, ioctl, import, index, int, join, keys, kill*, + last, lc, lcfirst, lchown*, length, link*, local, localtime, log, lstat, m//, map, mkdir, my, next, no, oct, open, opendir, ord, pack, pipe, pop, pos, print, printf, push, q//, qq//, qw//, - qx//*, quotemeta, rand, read, readdir, redo, ref, rename, + qx//*, quotemeta, rand, read, readdir, readlink*, redo, ref, rename, require, reset, return, reverse, rewinddir, rindex, rmdir, s///, scalar, seek, seekdir, select(internal), - select (system call)*, setpwent, shift, sin, sleep, - sort, splice, split, sprintf, sqrt, srand, stat, - study, substr, sysread, system*, syswrite, tell, + select (system call)*, setgrent, setpwent, shift, sin, sleep, + socketpair, sort, splice, split, sprintf, sqrt, srand, stat, + study, substr, symlink*, sysread, system*, syswrite, tell, telldir, tie, time, times*, tr///, uc, ucfirst, umask, undef, unlink*, unpack, untie, unshift, use, utime*, values, vec, wait, waitpid*, wantarray, warn, write, y/// @@ -482,12 +539,10 @@ The following functions were not implemented in the VMS port, and calling them produces a fatal error (usually) or undefined behavior (rarely, we hope): - chroot, dbmclose, dbmopen, flock, fork*, - getpgrp, getpriority, getgrent, getgrgid, - getgrnam, setgrent, endgrent, ioctl, link, lstat, - msgctl, msgget, msgsend, msgrcv, readlink, semctl, + chroot, dbmclose, dbmopen, fork*, getpgrp, getpriority, + msgctl, msgget, msgsend, msgrcv, semctl, semget, semop, setpgrp, setpriority, shmctl, shmget, - shmread, shmwrite, socketpair, symlink, syscall + shmread, shmwrite, syscall The following functions are available on Perls compiled with Dec C 5.2 or greater and running VMS 7.0 or greater: @@ -513,36 +568,25 @@ your copy of Perl: getsockopt, listen, recv, select(system call)*, send, setsockopt, shutdown, socket -The following function is available on Perls built on 64 bit OpenVMS 8.2 -with hard links enabled on an ODS-5 formatted build disk. If someone with -an OpenVMS 7.3-1 system were to modify configure.com and test the results, -this feature can be brought back to OpenVMS 7.3-1 and later. Hardlinks -must be enabled on the build disk because if the build procedure sees -this feature enabled, it uses it. +The following function is available on Perls built on 64 bit OpenVMS v8.2 +with hard links enabled on an ODS-5 formatted build disk. CRTL support +is in principle available as of OpenVMS v7.3-1, and better configuration +support could detect this. link The following functions are available on Perls built on 64 bit OpenVMS -8.2 and can be implemented on OpenVMS 7.3-2 if someone were to modify -configure.com and test the results. (While in the build, at the time -of this writing, they have not been specifically tested.) +v8.2 and later. CRTL support is in principle available as of OpenVMS +v7.3-2, and better configuration support could detect this. getgrgid, getgrnam, getpwnam, getpwuid, setgrent, ttyname -The following functions are available on Perls built on 64 bit OpenVMS 8.2 -and later. (While in the build, at the time of this writing, they have -not been specifically tested.) +The following functions are available on Perls built on 64 bit OpenVMS v8.2 +and later. statvfs, socketpair -The following functions are expected to soon be available on Perls built -on 64 bit OpenVMS 8.2 or later with the RMS Symbolic link package. Use -of symbolic links at this time effectively requires the -DECC$POSIX_COMPLIANT_PATHNAMES to defined as 3, and operating in a -DECC$FILENAME_UNIX_REPORT mode. - - lchown, link, lstat, readlink, symlink =over 4 =item File tests @@ -634,15 +678,36 @@ if neither of the $! or $? status values are ones that would cause the native status to be interpreted as being what VMS classifies as SEVERE_ERROR severity for DCL error handling. -When the future POSIX_EXIT mode is active, C, the native status -code will be set to VMS condition value that will allow C programs -including the GNV package to automatically decode the original C<$!> -or <$?> or <$^E> settings unless those are all success values, in -which case it will be set for those programs to recover the value -255. If at the time C is called, the native VMS status value -is either of SEVERE_ERROR or ERROR severity, the native VMS -value will be used. See C<$?> for a description on decoding the -native VMS value to recover the original exit status. +When the future POSIX_EXIT mode is active, C, the native VMS exit +status value will have either one of the C<$!> or C<$?> or C<$^E> or +the UNIX value 255 encoded into it in a way that the effective original +value can be decoded by other programs written in C, including Perl +and the GNV package. As per the normal non-VMS behavior of C if +either C<$!> or C<$?> are non-zero, one of those values will be +encoded into a native VMS status value. If both of the UNIX status +values are 0, and the C<$^E> value is set one of ERROR or SEVERE_ERROR +severity, then the C<$^E> value will be used as the exit code as is. +If none of the above apply, the UNIX value of 255 will be encoded into +a native VMS exit status value. + +Please note a significant difference in the behavior of C in +the future POSIX_EXIT mode is that it does not force a VMS +SEVERE_ERROR status on exit. The UNIX exit values of 2 through +255 will be encoded in VMS status values with severity levels of +SUCCESS. The UNIX exit value of 1 will be encoded in a VMS status +value with a severity level of ERROR. This is to be compatible with +how the VMS C library encodes these values. + +The minimum severity level set by C in a future POSIX_EXIT mode +may be changed to be ERROR or higher before that mode becomes fully active +depending on the results of testing and further review. If this is +done, the behavior of c in the future POSIX_EXIT will close enough +to the default mode that most DCL shell scripts will probably not notice +a difference. + +See C<$?> for a description of the encoding of the UNIX value to +produce a native VMS status containing it. + =item dump @@ -709,13 +774,14 @@ true, a warning message is printed, and C is returned. =item kill -In most cases, C is implemented via the CRTL's C -function, so it will behave according to that function's -documentation. If you send a SIGKILL, however, the $DELPRC system -service is called directly. This insures that the target -process is actually deleted, if at all possible. (The CRTL's C -function is presently implemented via $FORCEX, which is ignored by -supervisor-mode images like DCL.) +In most cases, C is implemented via the undocumented system +service <$SIGPRC>, which has the same calling sequence as <$FORCEX>, but +throws an exception in the target process rather than forcing it to call +C<$EXIT>. Generally speaking, C follows the behavior of the +CRTL's C function, but unlike that function can be called from +within a signal handler. Also, unlike the C in some versions of +the CRTL, Perl's C checks the validity of the signal passed in and +returns an error rather than attempting to send an unrecognized signal. Also, negative signal values don't do anything special under VMS; they're just converted to the corresponding positive value. @@ -835,9 +901,10 @@ and not traditional VMS behavior. =item utime LIST -Since ODS-2, the VMS file structure for disk files, does not keep -track of access times, this operator changes only the modification -time of the file (VMS revision date). +This operator changes only the modification time of the file (VMS +revision date) on ODS-2 volumes and ODS-5 volumes without access +dates enabled. On ODS-5 volumes with access dates enabled, the +true access time is modified. =item waitpid PID,FLAGS @@ -1047,39 +1114,51 @@ compiled with the _POSIX_EXIT macro set, the status value will contain the actual value of 0 to 255 returned by that program on a normal exit. -With the _POSIX_EXIT macro set, the exit code of zero is represented -as 1, and the values from 2 to 255 are encoded by the equation -VMS_status = 0x35a000 + (exit_code * 8) + 1. And in the special -case of value 1, VMS_status = 0x35a000 + 8 + 2 + 0x10000000. +With the _POSIX_EXIT macro set, the UNIX exit value of zero is +represented as a VMS native status of 1, and the UNIX values +from 2 to 255 are encoded by the equation: + + VMS_status = 0x35a000 + (unix_value * 8) + 1. + +And in the special case of unix value 1 the encoding is: + + VMS_status = 0x35a000 + 8 + 2 + 0x10000000. For other termination statuses, the severity portion of the -subprocess' exit status: if the severity was success or +subprocess' exit status is used: if the severity was success or informational, these bits are all 0; if the severity was warning, they contain a value of 1; if the severity was error or fatal error, they contain the actual severity bits, -which turns out to be a value of 2 for error and 4 for fatal error. +which turns out to be a value of 2 for error and 4 for severe_error. +Fatal is another term for the severe_error status. As a result, C<$?> will always be zero if the subprocess' exit status indicated successful completion, and non-zero if a warning or error occurred or a program compliant with encoding _POSIX_EXIT values was run and set a status. -How can you tell the difference? You can not unless you look at -the ${^CHILD_ERROR_NATIVE} code. The ${^CHILD_ERROR_NATIVE} code -returns the actual VMS status value and check the severity bits. -If the severity bits are clear, then the numeric value is code -passed back from the application. +How can you tell the difference between a non-zero status that is +the result of a VMS native error status or an encoded UNIX status? +You can not unless you look at the ${^CHILD_ERROR_NATIVE} value. +The ${^CHILD_ERROR_NATIVE} value returns the actual VMS status value +and check the severity bits. If the severity bits are equal to 1, +then if the numeric value for C<$?> is between 2 and 255 or 0, then +C<$?> accurately reflects a value passed back from a UNIX application. +If C<$?> is 1, and the severity bits indicate a VMS error (2), then +C<$?> is from a UNIX application exit value. In practice, Perl scripts that call programs that return _POSIX_EXIT -type status codes will be expecting those codes, and programs that -call traditional VMS programs will be expecting the previous behavior. +type status values will be expecting those values, and programs that +call traditional VMS programs will either be expecting the previous +behavior or just checking for a non-zero status. -And success is always the code 0. +And success is always the value 0 in all behaviors. When the actual VMS termination status of the child is an error, -internally the C<$!> value will be set to the closest UNIX code to -that error so that Perl scripts that test for error messages will -see the expected UNIX style error message instead of a VMS message. +internally the C<$!> value will be set to the closest UNIX errno +value to that error so that Perl scripts that test for error +messages will see the expected UNIX style error message instead +of a VMS message. Conversely, when setting C<$?> in an END block, an attempt is made to convert the POSIX value into a native status intelligible to @@ -1089,14 +1168,17 @@ SS$_NORMAL, and setting C<$?> to a non-zero value results in the generic failure status SS$_ABORT. See also L. With the future POSIX_EXIT mode set, setting C<$?> will cause the -code set to be encoded into a native VMS status code so that the -either the parent or child exit codes of 0 to 255 can be recovered -by C programs expecting _POSIX_EXIT behavior. If both a parent -and a child exit code are set, then it will be assumed that this -is a VMS status code to be passed through. The special code of -0xFFFF is almost a NOOP as it will cause the current native -VMS status in the C library to become the current native Perl -VMS status. +new value to also be encoded into C<$^E> so that the either the +original parent or child exit status values of 0 to 255 +can be automatically recovered by C programs expecting _POSIX_EXIT +behavior. If both a parent and a child exit value are non-zero, then it +will be assumed that this is actually a VMS native status value to +be passed through. The special value of 0xFFFF is almost a NOOP as +it will cause the current native VMS status in the C library to +become the current native Perl VMS status, and is handled this way +as consequence of it known to not be a valid native VMS status value. +It is recommend that only values in range of normal UNIX parent or +child status numbers, 0 to 255 are used. The pragma C makes C<$?> reflect the actual VMS exit status instead of the default emulation of POSIX status @@ -1105,7 +1187,9 @@ non-zero values to SS$_ABORT when setting C<$?> in an END block (but zero will still be converted to SS$_NORMAL). Do not use the pragma C with the future -POSIX_EXIT mode, as they are requesting conflicting actions. +POSIX_EXIT mode, as they are at times requesting conflicting +actions and the consequence of ignoring this advice will be +undefined to allow future improvements in the POSIX exit handling. =item $| @@ -1128,8 +1212,8 @@ problems. =head1 Revision date -This document was last updated on 14-Oct-2005, for Perl 5, -patchlevel 8. +This document was last updated on 3-Dec-2007, for Perl 5, +patchlevel 10. =head1 AUTHOR