text:
perlvms (1) - Linux Manuals
perlvms: VMS-specific documentation for Perl
perlvms - VMS-specific documentation for Perl
Gathered below are notes describing details of Perl 5's behavior on VMS. They are a supplement to the regular Perl 5 documentation, so we have focussed on the ways in which Perl 5 functions differently under VMS than it does under Unix, and on the interactions between Perl and the rest of the operating system. We haven't tried to duplicate complete descriptions of Perl features from the main Perl documentation, which can be found in the [.pod] subdirectory of the Perl distribution.We hope these notes will save you from confusion and lost sleep when writing Perl scripts on VMS. If you find we've missed something you think should appear here, please don't hesitate to drop a line to vmsperl [at] perl.org.
Directions for building and installing Perl 5 can be found in the file README.vms in the main source directory of the Perl distribution.Organization of Perl Images
Core Images
During the build process, three Perl images are produced. Miniperl.Exe is an executable image which contains all of the basic functionality of Perl, but cannot take advantage of Perl XS extensions and has a hard-wired list of library locations for loading pure-Perl modules. It is used extensively to build and test Perl and various extensions, but is not installed.Most of the complete Perl resides in the shareable image PerlShr.Exe, which provides a core to which the Perl executable image and all Perl extensions are linked. It is generally located via the logical name PERLSHR. While it's possible to put the image in SYS$SHARE to make it loadable, that's not recommended. And while you may wish to INSTALL the image for performance reasons, you should not install it with privileges; if you do, the result will not be what you expect as image privileges are disabled during Perl start-up.
Finally, Perl.Exe is an executable image containing the main entry point for Perl, as well as some initialization code. It should be placed in a public directory, and made world executable. In order to run Perl with command line arguments, you should define a foreign command to invoke this image.
Perl Extensions
Perl extensions are packages which provide both XS and Perl code to add new functionality to perl. (XS is a meta-language which simplifies writing C code which interacts with Perl, see perlxs for more details.) The Perl code for an extension is treated like any other library module - it's made available in your script through the appropriate "use" or "require" statement, and usually defines a Perl package containing the extension.The portion of the extension provided by the XS code may be connected to the rest of Perl in either of two ways. In the static configuration, the object code for the extension is linked directly into PerlShr.Exe, and is initialized whenever Perl is invoked. In the dynamic configuration, the extension's machine code is placed into a separate shareable image, which is mapped by Perl's DynaLoader when the extension is "use"d or "require"d in your script. This allows you to maintain the extension as a separate entity, at the cost of keeping track of the additional shareable image. Most extensions can be set up as either static or dynamic.
The source code for an extension usually resides in its own directory. At least three files are generally provided: Extshortname.xs (where Extshortname is the portion of the extension's name following the last "::"), containing the XS code, Extshortname.pm, the Perl library module for the extension, and Makefile.PL, a Perl script which uses the "MakeMaker" library modules supplied with Perl to generate a Descrip.MMS file for the extension.
Installing static extensions
Since static extensions are incorporated directly into PerlShr.Exe, you'll have to rebuild Perl to incorporate a new extension. You should edit the main Descrip.MMS or Makefile you use to build Perl, adding the extension's name to the "ext" macro, and the extension's object file to the "extobj" macro. You'll also need to build the extension's object file, either by adding dependencies to the main Descrip.MMS, or using a separate Descrip.MMS for the extension. Then, rebuild PerlShr.Exe to incorporate the new code.Finally, you'll need to copy the extension's Perl library module to the [.Extname] subdirectory under one of the directories in @INC, where Extname is the name of the extension, with all "::" replaced by "." (e.g. the library module for extension Foo::Bar would be copied to a [.Foo.Bar] subdirectory).
Installing dynamic extensions
In general, the distributed kit for a Perl extension includes a file named Makefile.PL, which is a Perl program which is used to create a Descrip.MMS file which can be used to build and install the files required by the extension. The kit should be unpacked into a directory tree not under the main Perl source directory, and the procedure for building the extension is simply
$ perl Makefile.PL ! Create Descrip.MMS $ mmk ! Build necessary files $ mmk test ! Run test code, if supplied $ mmk install ! Install into public Perl tree
VMS support for this process in the current release of Perl is sufficient to handle most extensions. (See the MakeMaker documentation for more details on installation options for extensions.)
- •
- the [.Lib.Auto.Arch$PVersExtname] subdirectory of one of the directories in @INC (where PVers is the version of Perl you're using, as supplied in $], with '.' converted to '_'), or
- •
- one of the directories in @INC, or
- •
- a directory which the extensions Perl library module passes to the DynaLoader when asking it to map the shareable image, or
- •
- Sys$Share or Sys$Library.
If the shareable image isn't in any of these places, you'll need to define a logical name Extshortname, where Extshortname is the portion of the extension's name after the last "::", which translates to the full file specification of the shareable image.
File specifications
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 (e.g. 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 "VMS::Filespec" 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, etc. 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 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 "./.../" in a Unix path is now translated to "[.^.^.^.]" instead of the traditional VMS "[...]". To be compatible with what MakeMaker expects, if a VMS path cannot be translated to a Unix path, it is passed through unchanged, so "unixify("[...]")" will return "[...]".
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.
Filename Case
Perl enables DECC$EFS_CASE_PRESERVE and DECC$ARGV_PARSE_STYLE by default. Note that the latter only takes effect when extended parse is set in the process in which Perl is running. When these features are explicitly disabled in the environment 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.N. B. 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 expectations 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 "SET PROCESS /CASE_LOOKUP=SENSITIVE"). Perl does not currently support case sensitivity on VMS, but it may in the future, so Perl programs should use the "File::Spec->case_tolerant" method to determine the state, and not the $^O variable.
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 "SHOW ROOT" 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.Wildcard expansion
File specifications containing wildcards are allowed both on the command line and within Perl globs (e.g. "<*.c>"). If the wildcard filespec uses VMS syntax, the resultant filespecs will follow VMS syntax; if a Unix-style filespec is passed in, Unix-style filespecs will be returned. Similar to the behavior of wildcard globbing for a Unix shell, one can escape command line wildcards with double quotation marks """ around a perl program command line argument. However, owing to the stripping of """ characters carried out by the C handling of argv you will need to escape a construct such as this one (in a directory containing the files PERL.C, PERL.EXE, PERL.H, and PERL.OBJ):
$ perl -e "print join(' ',@ARGV)" perl.* perl.c perl.exe perl.h perl.obj
in the following triple quoted manner:
$ perl -e "print join(' ',@ARGV)" """perl.*""" perl.*
In both the case of unquoted command line arguments or in calls to "glob()" VMS wildcard expansion is performed. (csh-style wildcard expansion is available if you use "File::Glob::glob".) If the wildcard filespec contains a device or directory specification, then the resultant filespecs will also contain a device and directory; otherwise, device and directory information are removed. VMS-style resultant filespecs will contain a full device and directory, while Unix-style resultant filespecs will contain only as much of a directory path as was present in the input filespec. For example, if your default directory is Perl_Root:[000000], the expansion of "[.t]*.*" will yield filespecs like ``perl_root:[t]base.dir'', while the expansion of "t/*/*" will yield filespecs like ``t/base.dir''. (This is done to match the behavior of glob expansion performed by Unix shells.)
Similarly, the resultant filespec will contain the file version only if one was present in the input filespec.
Input and output pipes to Perl filehandles are supported; the ``file name'' is passed to lib$spawn() for asynchronous execution. You should be careful to close any pipes you have opened in a Perl script, lest you leave any ``orphaned'' subprocesses around when Perl exits.You may also use backticks to invoke a DCL subprocess, whose output is used as the return value of the expression. The string between the backticks is handled as if it were the argument to the "system" operator (see below). In this case, Perl will wait for the subprocess to complete before continuing.
The mailbox (MBX) that perl can create to communicate with a pipe defaults to a buffer size of 8192 on 64-bit systems, 512 on VAX. The default buffer size is adjustable via the logical name PERL_MBX_SIZE provided that the value falls between 128 and the SYSGEN parameter MAXBUF inclusive. For example, to set the mailbox size to 32767 use "$ENV{'PERL_MBX_SIZE'} = 32767;" and then open and use pipe constructs. An alternative would be to issue the command:
$ Define PERL_MBX_SIZE 32767
before running your wide record pipe program. A larger value may improve performance at the expense of the BYTLM UAF quota.
PERL5LIB and PERLLIB
The PERL5LIB and PERLLIB environment elements work as documented in perl, except that the element separator is, by default, '|' instead of ':'. However, when running under a Unix shell as determined by the logical name "GNV$UNIX_SHELL", the separator will be ':' as on Unix systems. The directory specifications may use either VMS or Unix syntax.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 "TERM" to be "xterm", and the environment variable "DISPLAY" to exist. "xterm" must be in lower case.
$define TERM "xterm" $define DISPLAY "hostname:0.0"
Currently the value of "DISPLAY" 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 <PERLDB_PIDS> that is not a process identification number.
$define PERLDB_PIDS XXXX
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 usually not practical.
Starting Perl in the VMS debugger may change the program execution profile in a way that such problems are not reproduced.
The "kill" 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.
Command line
I/O redirection and backgrounding
Perl for VMS supports redirection of input and output on the command line, using a subset of Bourne shell syntax:- •
- "<file" reads stdin from "file",
- •
- ">file" writes stdout to "file",
- •
- ">>file" appends stdout to "file",
- •
- "2>file" writes stderr to "file",
- •
- "2>>file" appends stderr to "file", and
- •
- "2>&1" redirects stderr to stdout.
In addition, output may be piped to a subprocess, using the character '|'. Anything after this character on the command line is passed to a subprocess for execution; the subprocess takes the output of Perl as its input.
Finally, if the command line ends with '&', the entire command is run in the background as an asynchronous subprocess.
Command line switches
The following command line switches behave differently under VMS than described in perlrun. Note also that in order to pass uppercase switches to Perl, you need to enclose them in double-quotes on the command line, since the CRTL downcases all unquoted strings.On newer 64 bit versions of OpenVMS, a process setting now controls if the quoting is needed to preserve the case of command line arguments.
- -i
- If the "-i" switch is present but no extension for a backup copy is given, then inplace editing creates a new version of a file; the existing copy is not deleted. (Note that if an extension is given, an existing file is renamed to the backup file, as is the case under other operating systems, so it does not remain as a previous version under the original filename.)
- If the "-S" or "-"S"" switch is present and the script name does not contain a directory, then Perl translates the logical name DCL$PATH as a searchlist, using each translation as a directory in which to look for the script. In addition, if no file type is specified, Perl looks in each directory for a file matching the name specified, with a blank type, a type of .pl, and a type of .com, in that order.
- -u
- The "-u" switch causes the VMS debugger to be invoked after the Perl program is compiled, but before it has run. It does not create a core dump file.
Perl functions
As of the time this document was last revised, the following Perl functions were implemented in the VMS port of Perl (functions marked with * are discussed in more detail below):
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, endgrent, endpwent, eof, eval, exec*, exists, exit, exp, fileno, flock getc, getgrent*, getgrgid*, getgrnam, getlogin, getppid, getpwent*, getpwnam*, getpwuid*, glob, gmtime*, goto, 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, readlink*, redo, ref, rename, require, reset, return, reverse, rewinddir, rindex, rmdir, s///, scalar, seek, seekdir, select(internal), 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///
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, fork*, getpgrp, getpriority, msgctl, msgget, msgsend, msgrcv, semctl, semget, semop, setpgrp, setpriority, shmctl, shmget, 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:
The following functions are available on Perls built on VMS 7.2 or greater:
fcntl (without locking)
The following functions may or may not be implemented, depending on what type of socket support you've built into your copy of Perl:
accept, bind, connect, getpeername, gethostbyname, getnetbyname, getprotobyname, getservbyname, gethostbyaddr, getnetbyaddr, getprotobynumber, getservbyport, gethostent, getnetent, getprotoent, getservent, sethostent, setnetent, setprotoent, setservent, endhostent, endnetent, endprotoent, endservent, getsockname, getsockopt, listen, recv, select(system call)*, send, setsockopt, shutdown, socket
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.
The following functions are available on Perls built on 64 bit OpenVMS 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 v8.2 and later.
statvfs, socketpair
- File tests
The tests "-b", "-B", "-c", "-C", "-d", "-e", "-f",
"-o", "-M", "-s", "-S", "-t", "-T", and "-z" work as
advertised. The return values for "-r", "-w", and "-x"
tell you whether you can actually access the file; this may
not reflect the UIC-based file protections. Since real and
effective UIC don't differ under VMS, "-O", "-R", "-W",
and "-X" are equivalent to "-o", "-r", "-w", and "-x".
Similarly, several other tests, including "-A", "-g", "-k",
"-l", "-p", and "-u", aren't particularly meaningful under
VMS, and the values returned by these tests reflect whatever
your CRTL "stat()" routine does to the equivalent bits in the
st_mode field. Finally, "-d" returns true if passed a device
specification without an explicit directory (e.g. "DUA1:"), as
well as if passed a directory.
There are DECC feature logical names AND ODS-5 volume attributes that also control what values are returned for the date fields.
Note: Some sites have reported problems when using the file-access tests ("-r", "-w", and "-x") on files accessed via DEC's DFS. Specifically, since DFS does not currently provide access to the extended file header of files on remote volumes, attempts to examine the ACL fail, and the file tests will return false, with $! indicating that the file does not exist. You can use "stat" on these files, since that checks UIC-based protection only, and then manually check the appropriate bits, as defined by your C compiler's stat.h, in the mode value it returns, if you need an approximation of the file's protections.
- backticks
- Backticks create a subprocess, and pass the enclosed string to it for execution as a DCL command. Since the subprocess is created directly via "lib$spawn()", any valid DCL command string may be specified.
- binmode FILEHANDLE
The "binmode" operator will attempt to insure that no translation
of carriage control occurs on input from or output to this filehandle.
Since this involves reopening the file and then restoring its
file position indicator, if this function returns FALSE, the
underlying filehandle may no longer point to an open file, or may
point to a different position in the file than before "binmode"
was called.
Note that "binmode" is generally not necessary when using normal filehandles; it is provided so that you can control I/O to existing record-structured files when necessary. You can also use the "vmsfopen" function in the VMS::Stdio extension to gain finer control of I/O to files and devices with different record structures.
- crypt PLAINTEXT, USER
The "crypt" operator uses the "sys$hash_password" system
service to generate the hashed representation of PLAINTEXT.
If USER is a valid username, the algorithm and salt values
are taken from that user's UAF record. If it is not, then
the preferred algorithm and a salt of 0 are used. The
quadword encrypted value is returned as an 8-character string.
The value returned by "crypt" may be compared against the encrypted password from the UAF returned by the "getpw*" functions, in order to authenticate users. If you're going to do this, remember that the encrypted password in the UAF was generated using uppercase username and password strings; you'll have to upcase the arguments to "crypt" to insure that you'll get the proper value:
sub validate_passwd { my($user,$passwd) = @_; my($pwdhash); if ( !($pwdhash = (getpwnam($user))[1]) || $pwdhash ne crypt("\U$passwd","\U$name") ) { intruder_alert($name); } return 1; }
- die
"die" will force the native VMS exit status to be an SS$_ABORT code
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 "PERL_VMS_POSIX_EXIT" is active (see ``$?'' below), the native VMS exit status value will have either one of the $! or $? or $^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 "die" if either $! or $? 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 $^E value is set one of ERROR or SEVERE_ERROR severity, then the $^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 "die" in the "PERL_VMS_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 "die" in "PERL_VMS_POSIX_EXIT" mode may be changed to be ERROR or higher in the future depending on the results of testing and further review.
See ``$?'' for a description of the encoding of the Unix value to produce a native VMS status containing it.
- dump
- Rather than causing Perl to abort and dump core, the "dump" operator invokes the VMS debugger. If you continue to execute the Perl program under the debugger, control will be transferred to the label specified as the argument to "dump", or, if no label was specified, back to the beginning of the program. All other state of the program (e.g. values of variables, open file handles) are not affected by calling "dump".
- exec LIST
- A call to "exec" will cause Perl to exit, and to invoke the command given as an argument to "exec" via "lib$do_command". If the argument begins with '@' or '$' (other than as part of a filespec), then it is executed as a DCL command. Otherwise, the first token on the command line is treated as the filespec of an image to run, and an attempt is made to invoke it (using .Exe and the process defaults to expand the filespec) and pass the rest of "exec"'s argument to it as parameters. If the token has no file type, and matches a file with null type, then an attempt is made to determine whether the file is an executable image which should be invoked using "MCR" or a text file which should be passed to DCL as a command procedure.
- fork
- While in principle the "fork" operator could be implemented via (and with the same rather severe limitations as) the CRTL "vfork()" routine, and while some internal support to do just that is in place, the implementation has never been completed, making "fork" currently unavailable. A true kernel "fork()" is expected in a future version of VMS, and the pseudo-fork based on interpreter threads may be available in a future version of Perl on VMS (see perlfork). In the meantime, use "system", backticks, or piped filehandles to create subprocesses.
- getpwent
- getpwnam
- getpwuid
- These operators obtain the information described in perlfunc, if you have the privileges necessary to retrieve the named user's UAF information via "sys$getuai". If not, then only the $name, $uid, and $gid items are returned. The $dir item contains the login directory in VMS syntax, while the $comment item contains the login directory in Unix syntax. The $gcos item contains the owner field from the UAF record. The $quota item is not used.
- gmtime
- The "gmtime" operator will function properly if you have a working CRTL "gmtime()" routine, or if the logical name SYS$TIMEZONE_DIFFERENTIAL is defined as the number of seconds which must be added to UTC to yield local time. (This logical name is defined automatically if you are running a version of VMS with built-in UTC support.) If neither of these cases is true, a warning message is printed, and "undef" is returned.
- kill
In most cases, "kill" 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
$EXIT. Generally speaking, "kill" follows the behavior of the
CRTL's "kill()" function, but unlike that function can be called from
within a signal handler. Also, unlike the "kill" in some versions of
the CRTL, Perl's "kill" 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.
- qx//
- See the entry on "backticks" above.
- select (system call)
- If Perl was not built with socket support, the system call version of "select" is not available at all. If socket support is present, then the system call version of "select" functions only for file descriptors attached to sockets. It will not provide information about regular files or pipes, since the CRTL "select()" routine does not provide this functionality.
- stat EXPR
- Since VMS keeps track of files according to a different scheme than Unix, it's not really possible to represent the file's ID in the "st_dev" and "st_ino" fields of a "struct stat". Perl tries its best, though, and the values it uses are pretty unlikely to be the same for two different files. We can't guarantee this, though, so caveat scriptor.
- system LIST
The "system" operator creates a subprocess, and passes its
arguments to the subprocess for execution as a DCL command.
Since the subprocess is created directly via "lib$spawn()", any
valid DCL command string may be specified. If the string begins with
'@', it is treated as a DCL command unconditionally. Otherwise, if
the first token contains a character used as a delimiter in file
specification (e.g. ":" or "]"), an attempt is made to expand it
using a default type of .Exe and the process defaults, and if
successful, the resulting file is invoked via "MCR". This allows you
to invoke an image directly simply by passing the file specification
to "system", a common Unixish idiom. If the token has no file type,
and matches a file with null type, then an attempt is made to
determine whether the file is an executable image which should be
invoked using "MCR" or a text file which should be passed to DCL
as a command procedure.
If LIST consists of the empty string, "system" spawns an interactive DCL subprocess, in the same fashion as typing SPAWN at the DCL prompt.
Perl waits for the subprocess to complete before continuing execution in the current process. As described in perlfunc, the return value of "system" is a fake ``status'' which follows POSIX semantics unless the pragma "use vmsish 'status'" is in effect; see the description of $? in this document for more detail.
- time
- The value returned by "time" is the offset in seconds from 01-JAN-1970 00:00:00 (just like the CRTL's times() routine), in order to make life easier for code coming in from the POSIX/Unix world.
- times
- The array returned by the "times" operator is divided up according to the same rules the CRTL "times()" routine. Therefore, the ``system time'' elements will always be 0, since there is no difference between ``user time'' and ``system'' time under VMS, and the time accumulated by a subprocess may or may not appear separately in the ``child time'' field, depending on whether "times()" keeps track of subprocesses separately. Note especially that the VAXCRTL (at least) keeps track only of subprocesses spawned using "fork()" and "exec()"; it will not accumulate the times of subprocesses spawned via pipes, "system()", or backticks.
- unlink LIST
"unlink" will delete the highest version of a file only; in
order to delete all versions, you need to say
1 while unlink LIST;
You may need to make this change to scripts written for a Unix system which expect that after a call to "unlink", no files with the names passed to "unlink" will exist. (Note: This can be changed at compile time; if you "use Config" and $Config{'d_unlink_all_versions'} is "define", then "unlink" will delete all versions of a file on the first call.)
"unlink" will delete a file if at all possible, even if it requires changing file protection (though it won't try to change the protection of the parent directory). You can tell whether you've got explicit delete access to a file by using the "VMS::Filespec::candelete" operator. For instance, in order to delete only files to which you have delete access, you could say something like
sub safe_unlink { my($file,$num); foreach $file (@_) { next unless VMS::Filespec::candelete($file); $num += unlink $file; } $num; }
(or you could just use "VMS::Stdio::remove", if you've installed the VMS::Stdio extension distributed with Perl). If "unlink" has to change the file protection to delete the file, and you interrupt it in midstream, the file may be left intact, but with a changed ACL allowing you delete access.
This behavior of "unlink" is to be compatible with POSIX behavior and not traditional VMS behavior.
- utime LIST
- 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.
- waitpid PID,FLAGS
If PID is a subprocess started by a piped "open()" (see open),
"waitpid" will wait for that subprocess, and return its final status
value in $?. If PID is a subprocess created in some other way (e.g.
SPAWNed before Perl was invoked), "waitpid" will simply check once per
second whether the process has completed, and return when it has. (If
PID specifies a process that isn't a subprocess of the current process,
and you invoked Perl with the "-w" switch, a warning will be issued.)
Returns PID on success, -1 on error. The FLAGS argument is ignored in all cases.
Perl variables
The following VMS-specific information applies to the indicated ``special'' Perl variables, in addition to the general information in perlvar. Where there is a conflict, this information takes precedence.- %ENV
The operation of the %ENV array depends on the translation
of the logical name PERL_ENV_TABLES. If defined, it should
be a search list, each element of which specifies a location
for %ENV elements. If you tell Perl to read or set the
element "$ENV{"name"}", then Perl uses the translations of
PERL_ENV_TABLES as follows:
- This string tells Perl to consult the CRTL's internal "environ" array of key-value pairs, using name as the key. In most cases, this contains only a few keys, but if Perl was invoked via the C "exec[lv]e()" function, as is the case for some embedded Perl applications or when running under a shell such as GNV bash, the "environ" array may have been populated by the calling program.
- A string beginning with "CLISYM_"tells Perl to consult the CLI's symbol tables, using name as the name of the symbol. When reading an element of %ENV, the local symbol table is scanned first, followed by the global symbol table.. The characters following "CLISYM_" are significant when an element of %ENV is set or deleted: if the complete string is "CLISYM_LOCAL", the change is made in the local symbol table; otherwise the global symbol table is changed.
- Any other string
- If an element of PERL_ENV_TABLES translates to any other string, that string is used as the name of a logical name table, which is consulted using name as the logical name. The normal search order of access modes is used.
PERL_ENV_TABLES is translated once when Perl starts up; any changes you make while Perl is running do not affect the behavior of %ENV. If PERL_ENV_TABLES is not defined, then Perl defaults to consulting first the logical name tables specified by LNM$FILE_DEV, and then the CRTL "environ" array. This default order is reversed when the logical name GNV$UNIX_SHELL is defined, such as when running under GNV bash.
For operations on %ENV entries based on logical names or DCL symbols, the key string is treated as if it were entirely uppercase, regardless of the case actually specified in the Perl expression. Entries in %ENV based on the CRTL's environ array preserve the case of the key string when stored, and lookups are case sensitive.
When an element of %ENV is read, the locations to which PERL_ENV_TABLES points are checked in order, and the value obtained from the first successful lookup is returned. If the name of the %ENV element contains a semi-colon, it and any characters after it are removed. These are ignored when the CRTL "environ" array or a CLI symbol table is consulted. However, the name is looked up in a logical name table, the suffix after the semi-colon is treated as the translation index to be used for the lookup. This lets you look up successive values for search list logical names. For instance, if you say
$ Define STORY once,upon,a,time,there,was $ perl -e "for ($i = 0; $i <= 6; $i++) " - _$ -e "{ print $ENV{'story;'.$i},' '}"
Perl will print "ONCE UPON A TIME THERE WAS", assuming, of course, that PERL_ENV_TABLES is set up so that the logical name "story" is found, rather than a CLI symbol or CRTL "environ" element with the same name.
When an element of %ENV is set to a defined string, the corresponding definition is made in the location to which the first translation of PERL_ENV_TABLES points. If this causes a logical name to be created, it is defined in supervisor mode. (The same is done if an existing logical name was defined in executive or kernel mode; an existing user or supervisor mode logical name is reset to the new value.) If the value is an empty string, the logical name's translation is defined as a single "NUL" (ASCII "\0") character, since a logical name cannot translate to a zero-length string. (This restriction does not apply to CLI symbols or CRTL "environ" values; they are set to the empty string.)
When an element of %ENV is set to "undef", the element is looked up as if it were being read, and if it is found, it is deleted. (An item ``deleted'' from the CRTL "environ" array is set to the empty string.) Using "delete" to remove an element from %ENV has a similar effect, but after the element is deleted, another attempt is made to look up the element, so an inner-mode logical name or a name in another location will replace the logical name just deleted. In either case, only the first value found searching PERL_ENV_TABLES is altered. It is not possible at present to define a search list logical name via %ENV.
The element $ENV{DEFAULT} is special: when read, it returns Perl's current default device and directory, and when set, it resets them, regardless of the definition of PERL_ENV_TABLES. It cannot be cleared or deleted; attempts to do so are silently ignored.
Note that if you want to pass on any elements of the C-local environ array to a subprocess which isn't started by fork/exec, or isn't running a C program, you can ``promote'' them to logical names in the current process, which will then be inherited by all subprocesses, by saying
foreach my $key (qw[C-local keys you want promoted]) { my $temp = $ENV{$key}; # read from C-local array $ENV{$key} = $temp; # and define as logical name }
(You can't just say $ENV{$key} = $ENV{$key}, since the Perl optimizer is smart enough to elide the expression.)
Don't try to clear %ENV by saying "%ENV = ();", it will throw a fatal error. This is equivalent to doing the following from DCL:
You can imagine how bad things would be if, for example, the SYS$MANAGER or SYS$SYSTEM logical names were deleted.
At present, the first time you iterate over %ENV using "keys", or "values", you will incur a time penalty as all logical names are read, in order to fully populate %ENV. Subsequent iterations will not reread logical names, so they won't be as slow, but they also won't reflect any changes to logical name tables caused by other programs.
You do need to be careful with the logical names representing process-permanent files, such as "SYS$INPUT" and "SYS$OUTPUT". The translations for these logical names are prepended with a two-byte binary value (0x1B 0x00) that needs to be stripped off if you want to use it. (In previous versions of Perl it wasn't possible to get the values of these logical names, as the null byte acted as an end-of-string marker)
- $!
- The string value of $! is that returned by the CRTL's strerror() function, so it will include the VMS message for VMS-specific errors. The numeric value of $! is the value of "errno", except if errno is EVMSERR, in which case $! contains the value of vaxc$errno. Setting $! always sets errno to the value specified. If this value is EVMSERR, it also sets vaxc$errno to 4 (NONAME-F-NOMSG), so that the string value of $! won't reflect the VMS error message from before $! was set.
This variable provides direct access to VMS status values
in vaxc$errno, which are often more specific than the
generic Unix-style error messages in $!. Its numeric value
is the value of vaxc$errno, and its string value is the
corresponding VMS message string, as retrieved by sys$getmsg().
Setting $^E sets vaxc$errno to the value specified.
While Perl attempts to keep the vaxc$errno value to be current, if errno is not EVMSERR, it may not be from the current operation.
- $?
The ``status value'' returned in $? is synthesized from the
actual exit status of the subprocess in a way that approximates
POSIX wait(5) semantics, in order to allow Perl programs to
portably test for successful completion of subprocesses. The
low order 8 bits of $? are always 0 under VMS, since the
termination status of a process may or may not have been
generated by an exception.
The next 8 bits contain the termination status of the program.
If the child process follows the convention of C programs 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 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's 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 severe_error. Fatal is another term for the severe_error status.
As a result, $? will always be zero if the subprocess's 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 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 $? is between 2 and 255 or 0, then $? accurately reflects a value passed back from a Unix application. If $? is 1, and the severity bits indicate a VMS error (2), then $? is from a Unix application exit value.
In practice, Perl scripts that call programs that return _POSIX_EXIT 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 value 0 in all behaviors.
When the actual VMS termination status of the child is an error, internally the $! 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 $? in an END block, an attempt is made to convert the POSIX value into a native status intelligible to the operating system upon exiting Perl. What this boils down to is that setting $? to zero results in the generic success value SS$_NORMAL, and setting $? to a non-zero value results in the generic failure status SS$_ABORT. See also ``exit'' in perlport.
With the "PERL_VMS_POSIX_EXIT" logical name defined as ``ENABLE'', setting $? will cause the new value to be encoded into $^E so that either the original parent or child exit status values
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 it is known to not be a valid native VMS status value. It is recommend that only values in the range of normal Unix parent or child status numbers, 0 to 255 are used.The pragma "use vmsish 'status'" makes $? reflect the actual VMS exit status instead of the default emulation of POSIX status described above. This pragma also disables the conversion of non-zero values to SS$_ABORT when setting $? in an END block (but zero will still be converted to SS$_NORMAL).
Do not use the pragma "use vmsish 'status'" with "PERL_VMS_POSIX_EXIT" enabled, 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.
In general, with "PERL_VMS_POSIX_EXIT" enabled, more detailed information will be available in the exit status for DCL scripts or other native VMS tools, and will give the expected information for Posix programs. It has not been made the default in order to preserve backward compatibility.
N.B. Setting "DECC$FILENAME_UNIX_REPORT" implicitly enables "PERL_VMS_POSIX_EXIT".
- $|
- Setting $| for an I/O stream causes data to be flushed all the way to disk on each write (i.e. not just to the underlying RMS buffers for a file). In other words, it's equivalent to calling fflush() and fsync() from C.
Standard modules with VMS-specific differences
SDBM_File works properly on VMS. It has, however, one minor difference. The database directory file created has a .sdbm_dir extension rather than a .dir extension. .dir files are VMS filesystem directory files, and using them for other purposes could cause unacceptable problems.Revision date
Please see the git repository for revision history.AUTHOR
Charles Bailey bailey [at] cor.newman.upenn.edu Craig Berry craigberry [at] mac.com Dan Sugalski dan [at] sidhe.org John Malmberg wb8tyw [at] qsl.net


text:
Whether you're celebrating a special occasion, or no occasion, our Love and Romance flowers will set the right tone. Our collection includes lush romantic roses and romantic gifts like decadent chocolate.
Declare your love with romantic flowers designed by expert florists and have them delivered to your home or to the office. No matter the reason, your true love will be swept off her feet when you send a romantic gift from our Love and Romance collection.

subset: commoncrawl


text:
Return To Search
Legislation Text
Local Impact Statement Procedure Required
No — Permissive
Additional Documents
Primary Sponsors
Learn More : Glossary of Terms | The Legislative Process
The online versions of legislation provided on this website are not official. Enrolled bills are the final version passed by the Ohio General Assembly and presented to the Governor for signature. The official version of acts signed by the Governor are available from the Secretary of State's Office at 180 S. Civic Center Dr., Columbus, OH 43215.


text:
Former Howard Johnson in Indiana signs on with Magnuson
Accommodation is one of the biggest fixed costs travelers have and reducing that cost can lead to big savings! I'm sure many backpackers would sleep in a barn if it was the cheapest accommodation they could find!
No matter what your accommodation tastes may be, one thing everyone has in common is that no one wants to pay a fortune for it. In fact, one of the best ways to take a cheap holiday is to cut down on accommodation costs. Since you have to stay somewhere every night, reducing this expense can save you a lot of money off the total cost of your trip. Next to finding a cheap flight, finding free or inexpensive lodging will have the biggest impact on your budget.
Luckily, there are a number of ways travelers can find a decent place to stay without forking over their entire vacation fund:
Hospitality Exchanges
When I am looking for a Couchsurfing host, I use the following criteria:
- There has to be a picture with the profile. This just shows me that it's a real person.
- The profile has to be filled out – It shows they are interested and involved. Most people aren't going to spend the time to fill this out if they aren't going to be comfortable with strangers in their home. If someone hasn't bothered to fill out the profile, they probably don't use the site and I simply move on.
- They should have reviews – If other people have stayed with or have at least traveled with the host and had a good experience, you and your stuff will probably be fine. You might not get along with the host but at least you know they aren't a creep. The more positive reviews, the better.
- Verification helps – Couchsurfing offers different levels of verification. People can be verified by other travelers, with a mailing address, or with a credit card. Knowing that a person has been verified reduces the likelihood that they are going to be a crazy psycho killer. However, if someone isn't verified but has a lot of reviews, that's O.K. with me.
Hostels are another option for budget travelers. In hostels, rooms are dormitory-style with all the facilities shared. Many people think of hostels as a "young thing" and are not interested in sleeping in a dormitory. Yet people do not often realize that many hostels offer small rooms, singles, and doubles designed for solo travelers or couples. I have met people in hostels in their 50s and 60s. The myth they are dirty, gross places to stay designed for young people is wrong. Many hostels offer more amenities than hotels, the new ones are really clean, and as young people expect more comfort, hostels are cleaning up their ways. These aren't the hostels you see in movies.
Home Exchange
Another good way to get cheap accommodation is a home exchange program. This probably works best for older travelers who already own.
[bs-quote quote="There are few places you can find silence. Air travel could be the last fortress of solitude." style="style-15″ align="left" author_name="Regina Brett" author_job="American Author" author_avatar="https://kivraktic.com.tr/wp-content/uploads/travel-guides-quote-avatar.jpg"]
home. These programs have been around for a long time but are growing in popularity due to good marketing and word-of-mouth on the Internet. Home exchanges are just like they sound — for a set amount of time, you swap homes with a family from another country. It's a great way to live cheaply abroad.
Most people don't do this because they worry about security — but remember that the other family is trusting you with their home, too. Si
tes that facilitate home exchanges usually have various levels of verification and security similar to Couchsurfing. Families talk to each other over phone and e-mail, and there's no commitment if you find that it's not right for you. Most people who do this are like-minded, so the chances of something going wrong are slim. Moreover, the family sends a few people to check up on you when you arrive. You can get all the comforts of home (hotwater, laundry, etc.) while in another city, without paying for it.
For more information on home exchange, check out Home Exchange. This website was featured in the movie "The Holiday," which did a lot to alleviate people's fears over home exchange and bring this travel option into the mainstream. Some of the other home exchange websites are: Seniors Home Exchange, IHEN, and Home for Exchange.
Short Term Rentals
Similar to home exchanges, rentals allow people to stay in furnished apartments while traveling. These apartments can sometimes be cheaper than hotels and provide many more amenities. They are great if you plan to spend a week or more in one place. You'll get all the comforts of home without spending a fortune.


text:
Disney's The BFG comes to theaters tomorrow!
Get tickets now:
The talents of three of the world's greatest storytellers – Roald Dahl, Walt Disney and Steven Spielberg –
finally unite to bring Dahl's beloved classic "The BFG" to life. Directed by Spielberg, Disney's "The BFG" tells the imaginative story of a young girl and the Giant who introduces her to the wonders and perils of Giant Country. The BFG (Mark Rylance), while a giant himself, is a Big Friendly Giant and nothing like the other inhabitants of Giant Country. Standing 24-feet tall with enormous ears and a keen sense of smell, he is endearingly dim-witted and keeps to himself for the most part. Giants like Bloodbottler (Bill Hader) and Fleshlumpeater (Jemaine Clement) on the other hand, are twice as big and at least twice as scary and have been known to eat humans, while the BFG prefers Snozzcumber and Frobscottle. Upon her arrival in Giant Country, Sophie, a precocious 10-year-old girl from London, is initially frightened of the mysterious giant who has brought her to his cave, but soon comes to realize that the BFG is actually quite gentle and charming, and, having never met a giant before, has many questions. The BFG brings Sophie to Dream Country where he collects dreams and sends them to children, teaching her all about the magic and mystery of dreams. Having both been on their own in the world up until now, their affection for one another quickly grows, but Sophie's presence in Giant Country has attracted the unwanted attention of the other giants, who have become increasingly more bothersome. Sophie and the BFG soon depart for London to see the Queen (Penelope Wilton) and warn her of the precarious giant situation, but they must first convince the Queen and her maid, Mary (Rebecca Hall), that giants do indeed exist. Together, they come up with a plan to get rid of the giants once and for all.
Like Disney's The BFG on Facebook:
Follow Disney's The BFG on Twitter:
Follow Disney's The BFG on Instagram:


text:
Irrigation in Rensselaer
Find out how much a new irrigation watering system can do for your property. Clark's Cutting Edge Inc. is here to make it simple for you to enjoy all the benefits of an automatic watering system. Save time, water, and money while growing bigger and stronger plants in your garden. That way, you can enjoy your landscape more and spend less time maintaining it. When you are seeking irrigation systems experts in Rensselaer, look no further. We have what it takes to create an intuitive and effective watering system for you.
Irrigation Systems to Save Water
If it is created and installed correctly, a new watering system can significantly cut down on your water usage without sacrificing the health of your plants. There is no reason you must have a large water bill in order to maintain a beautiful garden. The following strategies can be employed to make your system as efficient as possible:
- • Directing water – many sprinkler systems do not spray their water exclusively on grass and other plants. All water that lands on sidewalks or driveways is wasted.
- • Even watering – If any area of your landscaping receives more water than it should, the excess simply runs off without being absorbed.
- • Scheduling – watering during the early and late hours results in less water evaporating or being blown away by the wind.
- • Proper spray – Water droplets should not be too mist-like to ensure it lands and is absorbed.
- • Automatic precision – Irrigation systems result in just the right amount of water being used, meaning none is wasted and your plants are not under-watered.
- • Moisture sensors – If it rains or is especially humid, sensors can shut your sprinklers off, meaning you take advantage of the natural water.
At the end of the day, an automatic water system does not just save you time, but it preserves water and reduces your bills. Learn more about how we can set up a system to maximize your savings.
Growing More Vibrant Plants Through the Right Sprinkler System
Saving water is great, but getting a system installed for your irrigation is really all about the plants. With the precise and perfectly consistent watering schedule that an automatic sprinkler system can provide, you can grow a healthier garden while spending less time up keeping it. Separate your plants into sections by type and integrate the sprinklers to water each section a different amount based on each specific need.
Custom Made Watering System
An important step in the creation of a watering system is the design process. We are able to work with you to determine exactly what the best way to meet your needs is. It is vital to examine your landscape to discover what soil condition, water source, plant material, and water pressure you have. We can also recommend what type of system would work best. Your garden areas may be more suitable for a drip system, allowing less water to be used and weed growth to be mitigated.
Learn More
When you are looking for irrigation contracting services in Rensselaer, Clark's Cutting Edge Inc. is the company that has the experience and expertise needed to make your dream a reality.


text:
You have no items in your shopping cart.
Purpose | Mineral Supplement |
Exp Date | 04/2025 |
Manufacturer | 21st Century |
Active Ingredients |
Directions |
Facts |
Warnings |
Keep out of Reach of Children Do not use if
Consult a health care provider prior to use
Stop use and contact your physician
Other Ingredients |
Other Information |
Disclaimer | Content and information on Hargraves Online Healthcare is provided for informational purposes only. It is not meant to substitute the advice provided by one's physician or any other medical professional. You should not use the information contained herein for diagnosing or treating a health problem or disease, or prescribing medication. If you have or suspect that you have a medical problem, immediately contact your health care provider. Information and statements regarding dietary supplements have not been evaluated by the Food and Drug Administration and are not intended to diagnose, treat, cure, or prevent any disease. While we work extremely hard to ensure that all product information is correct, manufacturers sometimes change their logos, packaging and products. You should use our site as a reference, carefully read all product packaging, and contact the manufacturer with any questions before using a product. We are not liable for inaccuracies or misstatements about products. Customer reviews are provided for informational purposes only. Customer reviews reflect the individual reviewer's results and experiences only and are not verified or endorsed by Hargraves Online Healthcare. Actual results may vary among users. |
Shipping Policy
FREE Domestic shipping with orders over $50
We strive at getting your order to you as quickly as possible!
We process orders (Monday through Friday 8:00 a.m. to 3:30 p.m. EST)
- Hargravesotc.com ships most its products via USPS, however, for certain items we may use FedEx or UPS
- For orders over $50, shipping is free for customers residing in the Continental United States ONLY. For all other orders in the US that are less than $50, there will be a flat rate fee of $2.99
- International orders will be calculated at the time of checkout
Hargraves Online Healthcare reserves the right to switch the shipping method to a more economical option.
Large Quantity Orders
- Hargraves Online Healthcare is not a warehouse distributor. If you would like to place large quantity orders of 100 or more please email us at email@example.com we will do our best to give the best price possible. However, our free shipping policy does not apply to these large quantity orders. Shipping charges will apply and is recommended to add Route Shipping Protection.
Split Shipments
- On occasion if orders are large or heavy, we may ship them in multiple shipments.
Delivery Time for United States and International Orders
- Due to the Covid-19 global pandemic - high shipping volumes & shipping times for USPS will/may be extended, standard shipments are expected to take up to 4-12 business days or longer, priority shipments are expected to take 2-5 business days or longer, and are NOT GUARANTEED. International orders may take up to 30 days or longer.
Delays by USPS are out of our Control!
- Orders with tracking info stating "In Transit, Arriving Late" by USPS is still scheduled to arrive but is delayed due to high shipping volumes. If your package states this we ask that you allow extra time for your package to arrive.
- Orders received by 3:30 p.m. EST will ship the same day. Orders received after 3:30 p.m. EST will ship the next business day. Any orders placed after 3:30 p.m. EST on Friday will ship the following business day.
- Due to the effects of Covid-19 high volumes at sorting facilities and the labor shortage across the country there are no guarantees of packages arriving on time.
- If orders are placed after 3:30 pm EST they will be shipped the next business day (may be delayed due to the effects of Covid-19 with high shipping volumes & the labor shortage)
(Not Guaranteed)(Non Refundable) - During the holiday's shipments will be delayed.
- If orders are placed after 3:30 pm EST they will be shipped the next business day.
- If shipments do not arrive within the 2-5 business day's (in the US) please contact USPS; all refunds are issued through USPS. https://www.usps.com/help/refunds.htm#pme
- Orders that are placed Monday-Wednesday before 3:00pm EST will ship the same day and should receive your order in 2 business days.
- Orders that are placed on a Thursday (during our business hours) will ship the same day, however will not be delivered until the following Tuesday.
Orders placed after Friday 3 pm EST, or on Saturday or Sunday, will not ship until the NEXT BUSINESS DAY.
- If orders are placed on Friday before 3pm EST packages will not arrive until the following Tuesday. Any order placed after 3pm EST on Friday, Saturday or Sunday will not ship until the following business day.
(Not Guaranteed)(Non Refundable)
(Not Guaranteed) (Non-Refundable)
- Orders must be placed by 3:30 pm EST to be shipped out the same day (All International deliveries can take up to 30 business days or longer due to the labor shortage and effects of Covid-19 along with high shipping volumes (may cause additional delays)
Incorrect Address or Corrections
- Shipping charges will NOT be refunded if any of these circumstances apply; Any package that is refused or undeliverable due to customer refusing package, customer changing their mind, insufficient address or incorrect address
- If the incorrect address is input and we are not notified before the shipment goes out Hargravesotc.com holds no responsibility for replacing the item(s) or issuing a refund.
Damaged Products
- We understand that sometimes our customers receive damaged products due to shipping vendors which include USPS, Fed-Ex, or UPS handling.
- Any customer that has chosen priority (expedited) shipping (2-3 business days) and receive packages that are damaged due to mishandling of shipping vendors; customers must file a claim with the shipping vendor they chose to deliver their package.
(Hargraves Online Healthcare is not liable for replacing these items)
Lost or Stolen Items
- Please refer to our Missing & Lost Packages Policy Page
DOT Restrictions on Air Shipments
- The U.S. Department of Transportation (DOT) prohibits air shipment of items that may contribute to a fire or other mishap during shipping.
Restricted items include:
- Aerosol-type products or medications in pressurized spray cans, such as hairspray, shaving cream and inhalers. Products that contain flammable, volatile or corrosive chemicals, such as fragrances, nail polish remover and bunion treatments.
- Hargraves Online Healthcare is committed to getting your order to you as quickly as possible, but also safely and responsibly, in compliance with DOT rules. That's why we require ground only delivery for orders that contain DOT restricted products.


text:
Family Log-In
Click Here
Subscribe to Updates
Please enter your story and choose an optional photo in the space provided below. When you have finished, click the "Preview" button to review or check your story before submission.
Choose a photo from the list of available photos. If you would like to use a photo of your own please upload it using the "Share a Photo" feature and it will become available here.


text:
FUTURES tutorial
r.futures.* is an implementation of FUTure Urban-Regional Environment Simulation (FUTURES) which is a model for multilevel simulations of emerging urban-rural landscape structure. FUTURES produces regional projections of landscape patterns using coupled submodels that integrate nonstationary drivers of land change: per capita demand (DEMAND submodel), site suitability (POTENTIAL submodel), and the spatial structure of conversion events (PGA submodel).
This tutorial shows how to prepare data and run the model. You can download sample dataset and simulate urban growth in The Triangle, region in the Piedmont of North Carolina in the United States with rapidly growing cities Raleigh, Durham and Chapel Hill.
This tutorial requires basic knowledge of GRASS GIS. If you haven't used GRASS GIS before, you may want to first go through some of the introductory tutorials or alternative workshops linked from the See also section.
Required software includes:
- addons
- R (≥ 3.0.2) - needed for r.futures.potential
- SciPy - useful for r.futures.demand
Input data used in this tutorial
Download sample dataset containing:
- digital elevation model (NED)
- NLCD 1992/2001 Retrofit Land Cover Change Product
- transportation network (TIGER)
- county boundaries (TIGER)
- protected areas (Secured Lands)
- cities above 20000 (USGS)
- county population past estimates and future projections (NC OSBM) per county (nonspatial)
Download sample data and unzip it. Create grassdata directory on your disk (or use the one you already have) and move there Location futures_ncspm. Launch GRASS GIS and select your grassdata directory, Location futures_ncspm and Mapset practice1.
Install addons:
g.extension r.futures
g.extension r.sample.category
Close GUI and restart it:
To install the required R packages, go to the command line terminal which was started with GRASS GIS and R:
This starts the R command line where you need to execute the following code (and go through any dialogs about installation if R shows them):
install.packages(c("MuMIn", "lme4", "optparse", "rgrass7"))
Initial steps and data preparation
First we will set computational region of our analyses to an extent covering our study area and so that the cells are aligned with one of our landuse rasters:
g.region raster=landuse_2011 -p
We will derive urbanized areas from NLCD dataset for year 1992, 2001 and 2011 by extracting categories category 21 - 24 into a new binary map where developed is 1, undeveloped 0 and NULL (no data) is area unsuitable for development (water, wetlands, protected areas). First we will convert protected areas from vector to raster and set NULLs to zeros (for simpler raster algebra expression in the next step):
v.to.rast input=protected_areas output=protected_areas use=val
r.null map=protected_areas null=0
And then create rasters of developed/undeveloped areas using raster algebra:
r.mapcalc "urban_1992 = if(landuse_1992 >= 21 && landuse_1992 <= 24, 1, if(landuse_1992 == 11 || landuse_1992 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2001 = if(landuse_2001 >= 21 && landuse_2001 <= 24, 1, if(landuse_2001 == 11 || landuse_2001 >= 90 || protected_areas, null(), 0))"
r.mapcalc "urban_2011 = if(landuse_2011 >= 21 && landuse_2011 <= 24, 1, if(landuse_2011 == 11 || landuse_2011 >= 90 || protected_areas, null(), 0))"
We will convert vector counties to raster with the values of the FIPS attribute which links to population file:
v.to.rast input=counties type=area use=attr attribute_column=FIPS output=counties
If we need to run FUTURES only for smaller number of counties, we can extract them based on the identifier:
v.to.rast input=counties type=area where="FIPS in (37183, 37101)" use=attr attribute_column=FIPS output=counties_subset
Before further steps, we will set our working directory so that the input population files and text files
we are going to create are saved in one directory and easily accessible.
You can do that from menu Settings → GRASS working environment → Change working directory.
Select (or create) a directory and move there the downloaded files population_projection.csv and population_trend.csv.
Potential submodel
Module r.futures.potential implements POTENTIAL submodel as a part of FUTURES land change model. POTENTIAL is implemented using a set of coefficients that relate a selection of site suitability factors to the probability of a place becoming developed. This is implemented using the parameter table in combination with maps of those site suitability factors (mapped predictors). The coefficients are obtained by conducting multilevel logistic regression in R with package lme4 where the coefficients may vary by county. The best model is selected automatically using dredge function from package MuMIn.
First, we will derive couple of predictors.
We will derive slope in degrees from digital elevation model using r.slope.aspect module:
r.slope.aspect elevation=elevation_30m slope=slope
Distance from lakes/rivers
First we will extract category Open Water from 2011 NLCD dataset:
r.mapcalc "water = if(landuse_2011 == 11, 1, null())"
Then we compute the distance to water with module r.grow.distance and set color table to shades of blue:
r.grow.distance input=water distance=dist_to_water
r.colors -n map=dist_to_water color=blues
Distance from protected areas
We will use raster protected of protected areas we already created, but we will set NULL values to zero. We compute the distance to protected areas with module r.grow.distance and set color table from green to red:
r.null map=protected_areas setnull=0
r.grow.distance input=protected_areas distance=dist_to_protected
r.colors map=dist_to_protected color=gyr
We will smooth the transition between forest and other land use, see NLCD category Open Water:
r.mapcalc "forest = if(landuse_2011 >= 41 && landuse_2011 <= 43, 1, 0)"
r.neighbors -c input=forest output=forest_smooth size=15 method=average
r.colors map=forest_smooth color=ndvi
Travel time to cities
Here we will compute travel time to cities (> population 20000) as cumulative cost distance where cost is defined as travel time on roads. First we specify the speed on different types of roads. We copy the roads raster into our mapset so that we can change it by adding a new attribute field speed. Then we assign speed values (km/h) based on the type of road:
g.copy vector=roads,myroads
v.db.addcolumn map=myroads columns="speed double precision"
v.db.update map=myroads column=speed value=50 where="MTFCC = 'S1400'"
v.db.update map=myroads column=speed value=100 where="MTFCC IN ('S1100', 'S1200')"
Now we rasterize the selected road types using the speed values from the attribute table as raster values.
v.to.rast input=myroads type=line where="MTFCC IN ('S1100', 'S1200', 'S1400')" output=roads_speed use=attr attribute_column=speed
We set the rest of the area to low speed and recompute the speed as time to travel through a 30m cell in minutes:
r.null map=roads_speed null=5
r.mapcalc "roads_travel_time = 1.8 / roads_speed"
Finally we compute the travel time to larger cities using r.cost:
r.cost input=roads_travel_time output=travel_time_cities start_points=cities_20000
r.colors map=travel_time_cities color=byr
Road density
We will rasterize roads and use moving window analysis (r.neighbors) to compute road density:
v.to.rast input=roads output=roads use=val
r.null map=roads null=0
r.neighbors -c input=roads output=road_dens size=25 method=average
Distance to interchanges
We will consider TIGER roads of type Ramp as interchanges, rasterize them and compute euclidean distance to them:
v.to.rast input=roads type=line where="MTFCC = 'S1630'" output=interchanges use=val
r.grow.distance -m input=interchanges distance=dist_interchanges
Development pressure
We compute development pressure with r.futures.devpressure. Development pressure is a predictor based on number of neighboring developed cells within search distance, weighted by distance. The development pressure variable plays a special role in the model, allowing for a feedback between predicted change and change in subsequent steps.
r.futures.devpressure -n input=urban_2011 output=devpressure_1 method=gravity size=10 gamma=1 scaling_factor=1
r.futures.devpressure -n input=urban_2011 output=devpressure_0_5 method=gravity size=30 gamma=0.5 scaling_factor=0.1
When gamma increases, development influence decreases more rapidly with distance. Size is half the size of the moving window. When gamma is low, local development influences more distant places. We will derive 2 layers with different gamma and size parameters for the potential statistical model.
Rescaling variables
First we will look at the ranges of our predictor variables by running a short Python code snippet in Python tab in GUI:
for name in ['slope', 'dist_to_water', 'dist_to_protected', 'forest_smooth', 'travel_time_cities', 'road_dens', 'dist_interchanges', 'devpressure_0_5', 'devpressure_1']:
minmax = grass.raster_info(name)
print name, minmax['min'], minmax['max']
We will rescale some of our input variables:
r.mapcalc "dist_to_water_km = dist_to_water / 1000"
r.mapcalc "dist_to_protected_km = dist_to_protected / 1000"
r.mapcalc "dist_interchanges_km = dist_interchanges / 1000"
r.mapcalc "road_dens_perc = road_dens * 100"
r.mapcalc "forest_smooth_perc = forest_smooth * 100"
To sample only in the analyzed counties, we will clip development layer:
r.mapcalc "urban_2011_clip = if(counties, urban_2011)"
To estimate the number of sampling points, we can use r.report to report number of developed/undeveloped cells and their ratio.
r.report map=urban_2011 units=h,c,p
We will sample the predictors and the response variable with 10000 random points in undeveloped areas and 2000 points in developed area:
r.sample.category input=urban_2011_clip output=sampling sampled=counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities npoints=10000,2000
The attribute table can be exported as CSV file (not necessary step):
v.db.select map=sampling columns=urban_2011_clip,counties,devpressure_0_5,devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities separator=comma file=samples.csv
Development potential
Now we find best model for predicting urbanization using r.futures.potential which wraps an R script.
We can play with different combinations of predictors, for example:
r.futures.potential input=sampling output=potential.csv columns=devpressure_0_5,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,road_dens_perc,dist_to_water_km,dist_to_protected_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties
Or we can run R dredge function to find "best" model. We can specify minimum and maximum number of predictors the final model should use.
r.futures.potential -d input=sampling output=potential.csv columns=devpressure_1,slope,road_dens_perc,forest_smooth_perc,dist_to_water_km,dist_to_protected_km,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties min_variables=4 max_variables=7
You can then open the output file potential.csv, which is a CSV file with tabs as separators.
For this tutorial, the final potential is created with:
r.futures.potential input=sampling output=potential.csv columns=devpressure_1,slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities developed_column=urban_2011_clip subregions_column=counties --o
Demand submodel
First we will mask out roads so that they don't influence into per capita land demand relation.
v.to.rast input=roads type=line output=roads_mask use=val
r.mask roads_mask -i
We will use r.futures.demand which derives the population vs. development relation. The relation can be linear/logarithmic/logarithmic2/exponential/exponential approach. Look for examples of the different relations in the manual.
- linear: y = A + Bx
- logarithmic: y = A + Bln(x)
- logarithmic2: y = A + B * ln(x - C) (requires SciPy)
- exponential: y = Ae^(BX)
- exp_approach: y = (1 - e^(-A(x - B))) + C (requires SciPy)
The format of the input population CSV files is described in the manual. It is important to have synchronized categories of subregions and the column headers of the CSV files (in our case FIPS number). How to simply generate the list of years (for which demand is computed) is described in r.futures.demand manual, for example run this in Python console:
','.join([str(i) for i in range(2011, 2036)])
Then we can create the DEMAND file:
r.futures.demand development=urban_1992,urban_2001,urban_2011 subregions=counties observed_population=population_trend.csv projected_population=population_projection.csv simulation_times=2011,2012,2013,2014,2015,2016,2017,2018,2019,2020,2021,2022,2023,2024,2025,2026,2027,2028,2029,2030,2031,2032,2033,2034,2035 plot=plot_demand.pdf demand=demand.csv separator=comma
In your current working directory, you should find files plot_demand.png and demand.csv.
If you have SciPy installed, you can experiment with other methods for fitting the functions:
r.futures.demand ... method=logarithmic2
r.futures.demand ... method=exp_approach
If necessary, you can create a set of demand files produced by fitting each method separately and then pick for each county the method which seems best and manually create a new demand file.
When you are finished, remove the mask as it is not needed for the next steps.
r.mask -r
Patch calibration
Patch calibration can be a very time consuming computation. First we derive patches of new development by comparing historical and latest development. We can run this on the entire area and keep only patches with minimum size 2 cells (1800 = 2 x 30 x 30 m).
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=counties patch_sizes=patches.txt patch_threshold=1800 -l
We obtained a file patches.txt (used later in the PGA) - a patch size distribution file - containing sizes of all found patches.
We can look at the distribution of the patch sizes:
from matplotlib import pyplot as plt
with open('patches.txt') as f:
patches = [int(patch) for patch in f.readlines()]
plt.hist(patches, 2000)
At this point, we start the calibration to get best parameters of patch shape (for this tutorial, this step can be skipped and the suggested parameters are used). First we select only one county to
v.to.rast input=counties type=area where="FIPS == 37183" use=attr attribute_column=FIPS output=calib_county
g.region raster=calib_county zoom=calib_county
r.futures.calib development_start=urban_1992 development_end=urban_2011 subregions=calib_county patch_sizes=patches.txt calibration_results=calib.csv patch_threshold=1800 repeat=5 compactness_mean=0.1,0.3,0.5,0.7,0.9 compactness_range=0.1,0.05 discount_factor=0.1,0.3,0.5,0.7,0.9 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities demand=demand.csv devpot_params=potential.csv num_neighbors=4 seed_search=2 development_pressure=devpressure_1 development_pressure_approach=gravity n_dev_neighbourhood=10 gamma=1 scaling_factor=1 --o
FUTURES simulation
We will switch back to our previous region:
g.region raster=landuse_2011 -p
Now we have all the inputs necessary for running r.futures.pga:
The entire command is here:
r.futures.pga subregions=counties developed=urban_2011 predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 demand=demand.csv discount_factor=0.3 compactness_mean=0.2 compactness_range=0.1 patch_sizes=patches.txt num_neighbors=4 seed_search=2 random_seed=1 output=final output_series=final
Quick description
The command parameters and their values:
- raster map of counties with their categories
... subregions=counties ...
- raster of developed (1), undeveloped (0) and NULLs for undevelopable areas
... developed=urban_2011 ...
- predictors selected with r.futures.potential and their coefficients in a potential.csv file. The order of predictors must match the order in the file and the categories of the counties must match raster counties.
... predictors=slope,forest_smooth_perc,dist_interchanges_km,travel_time_cities devpot_params=potential.csv ...
- initial development pressure computed by r.futures.devpressure, it's important to set here the same parameters
... development_pressure=devpressure_1 n_dev_neighbourhood=10 development_pressure_approach=gravity gamma=1 scaling_factor=1 ...
- per capita land demand computed by r.futures.demand, the categories of the counties must match raster counties.
... demand=demand.csv ...
- patch parameters from the calibration step
... discount_factor=0.3 compactness_mean=0.4 compactness_range=0.08 patch_sizes=patches.txt ...
- recommended parameters for patch growing algorithm
... num_neighbors=4 seed_search=2 ...
- set random seed for repeatable results or set flag -s to generate seed automatically
... random_seed=1 ...
- specify final output map and optionally basename for intermediate raster maps
output=final output_series=final
Scenarios involving policies that encourage infill versus sprawl can be explored using the incentive_power parameter, which uses a power function to transform the evenness of the probability gradient in POTENTIAL.
The default value is 1. You can change the power to a number between 0.25 and 4 to test urban sprawl/infill scenarios. Higher power leads to infill behavior, lower power to urban sprawl.
Follow a tutorial how to make an animation from the results.


text:
1 Chronicles 3
King James Version
3 Now these were the sons of David, which were born unto him in Hebron; the firstborn Amnon, of Ahinoam the Jezreelitess; the second Daniel, of Abigail the Carmelitess:
2 The third, Absalom the son of Maachah the daughter of Talmai king of Geshur: the fourth, Adonijah the son of Haggith:
3 The fifth, Shephatiah of Abital: the sixth, Ithream by Eglah his wife.
4 These six were born unto him in Hebron; and there he reigned seven years and six months: and in Jerusalem he reigned thirty and three years.
5 And these were born unto him in Jerusalem; Shimea, and Shobab, and Nathan, and Solomon, four, of Bathshua the daughter of Ammiel:
6 Ibhar also, and Elishama, and Eliphelet,
7 And Nogah, and Nepheg, and Japhia,
8 And Elishama, and Eliada, and Eliphelet, nine.
9 These were all the sons of David, beside the sons of the concubines, and Tamar their sister.
10 And Solomon's son was Rehoboam, Abia his son, Asa his son, Jehoshaphat his son,
11 Joram his son, Ahaziah his son, Joash his son,
12 Amaziah his son, Azariah his son, Jotham his son,
13 Ahaz his son, Hezekiah his son, Manasseh his son,
14 Amon his son, Josiah his son.
15 And the sons of Josiah were, the firstborn Johanan, the second Jehoiakim, the third Zedekiah, the fourth Shallum.
16 And the sons of Jehoiakim: Jeconiah his son, Zedekiah his son.
17 And the sons of Jeconiah; Assir, Salathiel his son,
18 Malchiram also, and Pedaiah, and Shenazar, Jecamiah, Hoshama, and Nedabiah.
19 And the sons of Pedaiah were, Zerubbabel, and Shimei: and the sons of Zerubbabel; Meshullam, and Hananiah, and Shelomith their sister:
20 And Hashubah, and Ohel, and Berechiah, and Hasadiah, Jushabhesed, five.
21 And the sons of Hananiah; Pelatiah, and Jesaiah: the sons of Rephaiah, the sons of Arnan, the sons of Obadiah, the sons of Shechaniah.
22 And the sons of Shechaniah; Shemaiah: and the sons of Shemaiah; Hattush, and Igeal, and Bariah, and Neariah, and Shaphat, six.
23 And the sons of Neariah; Elioenai, and Hezekiah, and Azrikam, three.
24 And the sons of Elioenai were, Hodaiah, and Eliashib, and Pelaiah, and Akkub, and Johanan, and Dalaiah, and Anani, seven.


text:
About the County
Our Mission
County Maps
Board of Commissioners
Job Opportunities
Disclaimer & Privacy Statement
Board of Commissioners Meetings
Building Inspections
Contracts & RFPs
County Codes & Ordinances
Economic Development Services
Planning & Zoning
Report a Pothole
Restaurant Inspections
Surveyor's Office
Affordable Housing Information
Dog Services & Shelter
Emergencies & Alerts
Health Services
Justice Court
Juvenile Services
Marriage Licenses
Public Safety
Recycling & Waste Management
Veteran Resources
Victim Assistance
Volunteer Opportunities
County Events
Maps & GIS Data
Marion County Parks
Points of Interest
Building Permits
Concealed Handgun License
Dog License
Food Handler Permit
Rental Assistance
Transportation Permits
Building Permit Fees
Civil Process Fees
Dog License Fees
Planning Fees
Recording Fees
Surveyor's Office Fees
System Development Charges
Waste Disposal Rates
County Fair Information
County Parks
Lost Dog
Recycling Locations
Road Projects
Voter Dropbox Locations
Birth Certificate
Marriage License
Property Records
Public Records
Survey Plats
Send Money to Adult in Custody
Property Taxes
Traffic Citations
Adoptable Dogs
Contracting Opportunities
Adult in Custody Lookup
Board Meetings
Assessor's Office
Business Services
Clerk's Office
Community Services
District Attorney
Health & Human Services
Housing Authority
Human Resources
Information Technology
Legal Counsel
Public Works
Sheriff's Office
Treasurer's Office
Contact Us
Emergency Contacts
Social Media Center
Marion County Legal Counsel's client is the legal entity of Marion County, Oregon. The Board of Commissioners is the governing body of the county. Office lawyers are prohibited from providing legal advice to the public or to parties other than the political subdivision and body politic of Marion County.
Cody HawkinsScott A. NorrisCody WaltermanJohn PettiferSelah Crisp
Gayle RachtmanErin Fox
Andrea Nofziger
The Office of Legal Counsel provides legal services to the Board of Commissioners, county departments, boards, commissions and to individual county employees when required by the Oregon Tort Claims Act. The Office of Legal Counsel has an attorney-client relationship with the County. County Counsel and Assistant Legal Counsels are appointed by and serve at the pleasure of the Board of Commissioners. The Office of Legal Counsel is exempt from civil service.
The office's legal services include representing the county in a variety of areas including tort claims, personnel actions and discrimination claims, labor matters, land use and planning appeals, public records matters, code enforcement, constitutional challenges, foreclosure and lien actions, nuisance abatement, civil forfeiture, real property matters, pension and benefit matters, environmental issues, road and right-of-way regulation, solid waste collection, disposal and franchising matters, fiscal and taxation matters. Legal services also include approving, modifying or disapproving contracts, agreements, ordinances, policies and other county actions.
555 Court St NE, Suite 5242Salem, OR 97301
P.O. Box 14500Salem, OR 97309
8:00 a.m. - 5:00 p.m. Monday-Friday
Phone: Fax: Email:
Get Directions


text:
- Brand:ELKLOOK
- Frame Size:Medium
- Lens Width: 49mm
- Lens Height: 35mm
- Frame Width:138mm
- Bridge Width:19mm
- Temple Length: 146mm
- Material: TR90
Unveil your ELKLOOK package to start a delightful unboxing journey. Here's what awaits inside:
Eco-Friendly Paper Packaging Box
A small step towards a greener planet. -
Cushioned Eyeglass Case
Your glasses' cozy home, easy to carry wherever you go. -
Soft Fabric Eyeglass Pouch
Gentle touch with flexible storage. -
Gentle Lens Cleaning Cloth
Soft embrace for crystal clear vision. -
Your Freshly Cleaned New Glasses Wrapped in Protective Film
Ready to meet the world with you, pristine from the start. -
Professional Pupillary Distance Ruler
Perfecting your vision, personalized to your eyes.


text:
Make your tailored pre-launch page for Satellite technicians
Empower Satellite technicians with Instapage to deliver impactful pre-launch page experiences and boost conversions.
Build landing pages that get results
Drive ad campaign performance using targeted landing pages. With over 500+ layouts, AI-content generation, built-in collaboration, Instablocks®, and quick page load technology, you can easily create landing pages that deliver an unparalleled user experience that gets more people buying.
Boost results through landing page optimization
Optimize your landing pages using Instapage's variety of testing tools. Track and analyze user behavior with heatmaps, run A/B testing to single-out the best performing version, or launch AI-assisted experiments that automatically analyze ad traffic and route it to best-performing.
Personalize experiences for higher engagement and ROI
Craft unique and high-performing landing pages that align with your ad messaging and resonate with your target audience. By crafting a landing page experience that resonates with your audience, you'll engage more visitors, maximize conversions, and reduce acquisition costs.
Maximize campaign efficiency with ad mapping
Efficiently manage campaigns by visualizing your ads and mapping them to corresponding landing pages in one place. Define what campaigns need a personalized experience and connect them with relevant ads to increase conversion rates and decrease CPA.
Power up landing pages with AI
Instantly create high-performing content for each audience segment and separate ad campaigns with the AI assistant. From catchy headlines to converting CTAs for A/B tests – access and use AI directly on your Instapage. No more writer's block or workflow interruptions.
Improve alignment across your creative team
Get your campaigns off the ground faster with efficient teamwork that happens in real time. Empower your team members to provide immediate feedback, make edits to page versions, and securely share information with outside stakeholders all from a single secure space.
Discover how to create your tailored pre-launch page for Satellite technicians
So, you're up against a challenge to create your tailored pre-launch page for Satellite technicians. You want it to be eye-catching and easy to navigate as well as easily discoverable on Google and effective in converting visitors into clients. The key question is, how exactly do you achieve all these goals for the most affordable cost possible?
The answer is just a step away with Instapage. It offers an easy-to-use platform that simplifies the process of creating professional and effective marketing pages tailored to specific industries. Its straightforward design tools and SEO-friendly features make sure your target audience discovers and engages with your site efficiently.
Here's how to build your tailored pre-launch page for Satellite technicians
- Start your subscription: Go to the Instapage price page, examine the subscription options, and select to sign up for a free trial or request a demo.
- Set up an account: Enter your email to sign up or authenticate yourself via Gmail.
- Start the web page creation process: Once you're in, explore your dashboard and proceed to make your tailored pre-launch page for Satellite technicians.
- Choose how to start—you have three options:
- Use a template: Pick from various templates based on your needs.
- Start from scratch: Choose a blank canvas to uniquely design your page.
- Upload a file: If you have a pre-designed page, you can upload it here.
- Select a template (if applicable): Look through the template gallery, preview different templates, and select one that matches your needs.
- Design and personalize: Once you select a template or start from scratch, you'll enter the editor. Here, you can personalize everything—from text to images and layout. Utilize Instapage's drag-and-drop interface to effortlessly add or modify elements.
- Preview, save, and publish your work: Regularly preview your page to see how it will be display to visitors. After finishing your design, save your work. You can then launch it immediately or schedule it to be released at a later time.
Remember, with Instapage, the process is simplified and designed to be straightforward, making it more convenient for you to create and handle professional pages. For more in-depth instructions, go to Instapage's guide here or sign up and start exploring our features today!
Get more out of Build your pre-launch page for Satellite technicians feature
Improve your Quality Score with quick load technology for landing pages
Increase conversions with content that aligns with your ads and audiences
Achieve maximum ROI by scaling your marketing initiatives
Leading the way in building high-performing landing pages
See how to build your pre-launch page for satellite technicians in action
Ready to skyrocket conversions?
Supercharge your ad campaigns with high-performing landing pages
Get started


text:
Extra baggage conditions
1. Taking extra baggage
1.1 When booking a flight, when checking in online and via My Trip, KLM offers the possibility of taking extra pieces of baggage above the baggage allowance at an extra fee, on the basis of the conditions of your ticket.
1.2 Please note that when departing from some airports, it is not possible to arrange extra baggage on KLM.com. In that case, please go to the desk at the airport to arrange extra baggage.
2. Conditions applying to pre-purchased extra baggage
2.1 The pre-purchased extra baggage can only be used in combination with the ticket you bought the extra baggage for. The pre-purchased extra baggage is personal and non-transferable. 2.2 The pre-purchased extra baggage is valid for a one-way journey (outbound or return journey) to the place of the stopover or the final destination, and exclusively for flights with KLM. 2.3 KLM's General Conditions of Carriage are an integral part of these conditions. 2.4 You are required to ensure that all the information you provide when making your reservation and purchasing the pre-purchased extra baggage is complete.
3. Refund
3.1 You are entitled to a refund of the specific costs of your pre-purchased extra baggage, if:
(I) KLM is unable to operate your flight, or (II) the baggage for which you have bought the pre-purchased extra baggage allowance is lost and is not found within a reasonable length of time.
3.2 You are not entitled to a refund if you decide to cancel your flight or take less baggage with you than you are entitled to on the basis of your pre-purchased extra baggage. If you decide to take more baggage than the total allowance, including the pre-purchased extra baggage, you pay the normal excess baggage fee for the excess amount.
3.3 If you are able to change your flight on the grounds of the fee conditions applicable to your ticket, then your pre-purchased extra baggage allowance will remain valid in combination with your amended ticket.
3.4 A refund request may only be submitted through our website.