10-22-2004
Quote:
UNIX is an infant compared to VMS
Not true -
see short history of UNIX - UNIX 1969 VMS - 1978
And I'm a Solaris System Administrator - haven't touched VMS in years. But I remember it fondly and laugh when folks believe it's going away - it's been said for 20 years. Just the same as NT was going to replace UNIX. Each has it's own strenght and weaknesses - sometime the greatest weakness is the marketing done by the folks trying to sell the product.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am looking for some help with writing a small script that will scan a range if subnets and count the number of reply.
If anyone has any shell programming experience with either perl or tcp/ip could you please give me a hand.. (1 Reply)
Discussion started by: veitcha
1 Replies
2. Shell Programming and Scripting
Does anyone know what a unix equivalent to the following OpenVms string would be?
variable1 = F$FAO("!123AS",file_create_time)
I can't seem to find the proper syntax of anything I try.
Thx!
J (1 Reply)
Discussion started by: prosserj
1 Replies
3. IP Networking
Hey,
I am learning to program a TCP server and managed to get it up and running (I am using Windows 98SE).
I can use the send function to send information to the client and I can use the recv function to ask the user to pass information through, but when I do so it only allows the client to... (1 Reply)
Discussion started by: KrazyGuyPaul
1 Replies
4. Programming
Hello there chaps.
First of all, i'm no TCP/IP-wiz, so forgive me if this is a stupid question.
I've been messing around with filetransfer using sockets, and there is one thing that confuses me.
This is how it's set up:
A server app listens on a port for a client connection.
When it... (3 Replies)
Discussion started by: crippe
3 Replies
5. Programming
We are in requirement to port relative file organization files from OpenVMS V7.1-1H2 to AIX Unix. These file contains multiple binary records each of 512 bytes but it could be possible that a few bytes are padded up to fill the record structure.
One of our thought process is to write a program... (1 Reply)
Discussion started by: S.P.Prasad
1 Replies
6. UNIX for Dummies Questions & Answers
I'm new to socket programming. Have a basic doubt.
I have a structure(global) at the server side.
I have two different client connecting to the server. Will the changes made by one client on the structure be visible to the other client when it accesses the same client? I'm creating a STREAM... (3 Replies)
Discussion started by: abc.working
3 Replies
7. Solaris
I was asked to look into a problem with a Sun Netra 440 in another department. On the server in question, the relevant 'uname -a' information is, "SunOS host1 5.9 Generic_118558-16 sun4u sparc SUNW,Netra-440". That information aside, while the other admin is logged into the ALOM, these errors are... (0 Replies)
Discussion started by: Borealis
0 Replies
8. HP-UX
Any takers on a seeminly simple question? (8 Replies)
Discussion started by: mrmurdock
8 Replies
9. Post Here to Contact Site Administrators and Moderators
Hello admins and moderators,
I was just wondering why you never opened an openVMS subforum under Operating Systems section. After all, openVMS is still active.
thanks. (0 Replies)
Discussion started by: milhan
0 Replies
LEARN ABOUT CENTOS
vmsish
vmsish(3pm) Perl Programmers Reference Guide vmsish(3pm)
NAME
vmsish - Perl pragma to control VMS-specific language features
SYNOPSIS
use vmsish;
use vmsish 'status'; # or '$?'
use vmsish 'exit';
use vmsish 'time';
use vmsish 'hushed';
no vmsish 'hushed';
vmsish::hushed($hush);
use vmsish;
no vmsish 'time';
DESCRIPTION
If no import list is supplied, all possible VMS-specific features are assumed. Currently, there are four VMS-specific features available:
'status' (a.k.a '$?'), 'exit', 'time' and 'hushed'.
If you're not running VMS, this module does nothing.
"vmsish status"
This makes $? and "system" return the native VMS exit status instead of emulating the POSIX exit status.
"vmsish exit"
This makes "exit 1" produce a successful exit (with status SS$_NORMAL), instead of emulating UNIX exit(), which considers "exit 1" to
indicate an error. As with the CRTL's exit() function, "exit 0" is also mapped to an exit status of SS$_NORMAL, and any other
argument to exit() is used directly as Perl's exit status.
"vmsish time"
This makes all times relative to the local time zone, instead of the default of Universal Time (a.k.a Greenwich Mean Time, or GMT).
"vmsish hushed"
This suppresses printing of VMS status messages to SYS$OUTPUT and SYS$ERROR if Perl terminates with an error status, and allows
programs that are expecting "unix-style" Perl to avoid having to parse VMS error messages. It does not suppress any messages from
Perl itself, just the messages generated by DCL after Perl exits. The DCL symbol $STATUS will still have the termination status, but
with a high-order bit set:
EXAMPLE:
$ perl -e"exit 44;" Non-hushed error exit
%SYSTEM-F-ABORT, abort DCL message
$ show sym $STATUS
$STATUS == "%X0000002C"
$ perl -e"use vmsish qw(hushed); exit 44;" Hushed error exit
$ show sym $STATUS
$STATUS == "%X1000002C"
The 'hushed' flag has a global scope during compilation: the exit() or die() commands that are compiled after 'vmsish hushed' will be
hushed when they are executed. Doing a "no vmsish 'hushed'" turns off the hushed flag.
The status of the hushed flag also affects output of VMS error messages from compilation errors. Again, you still get the Perl
error message (and the code in $STATUS)
EXAMPLE:
use vmsish 'hushed'; # turn on hushed flag
use Carp; # Carp compiled hushed
exit 44; # will be hushed
croak('I die'); # will be hushed
no vmsish 'hushed'; # turn off hushed flag
exit 44; # will not be hushed
croak('I die2'): # WILL be hushed, croak was compiled hushed
You can also control the 'hushed' flag at run-time, using the built-in routine vmsish::hushed(). Without argument, it returns the
hushed status. Since vmsish::hushed is built-in, you do not need to "use vmsish" to call it.
EXAMPLE:
if ($quiet_exit) {
vmsish::hushed(1);
}
print "Sssshhhh...I'm hushed...
" if vmsish::hushed();
exit 44;
Note that an exit() or die() that is compiled 'hushed' because of "use vmsish" is not un-hushed by calling vmsish::hushed(0) at
runtime.
The messages from error exits from inside the Perl core are generally more serious, and are not suppressed.
See "Perl Modules" in perlmod.
perl v5.16.3 2013-03-04 vmsish(3pm)