Sponsored Content
Top Forums Programming OpenVMS IPC and TCP/IP Programming Post 57306 by izy100 on Friday 22nd of October 2004 09:26:57 AM
Old 10-22-2004
Hmmm, I dun really mean it as a joke. I know that VMS is the king of clustering and I know that UNIX is an infant compared to VMS.

However, due to the high cost of maintenance, and lack of skilled ppl to support them, my company is indeed moving away from VMS.

I am still puzzled why are you moving in the opposite direction?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Tcp/ip programming

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

Converting an OpenVms .com to a UNIX ksh script

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

TCP Programming problems with 'recv'

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

Confusion about TCP/IP socket 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

Porting File from OPenVMS to AIX Unix

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

socket programming : client server IPC

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

errors on Netra-440: "IPC Warning: ipc: tcp_protocol: bad magic number"

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 OpenVMS 8.4 Users available?

Any takers on a seeminly simple question? (8 Replies)
Discussion started by: mrmurdock
8 Replies

9. Post Here to Contact Site Administrators and Moderators

OpenVMS forum

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
File::Spec::VMS(3pm)					 Perl Programmers Reference Guide				      File::Spec::VMS(3pm)

NAME
File::Spec::VMS - methods for VMS file specs SYNOPSIS
require File::Spec::VMS; # Done internally by File::Spec if needed DESCRIPTION
See File::Spec::Unix for a documentation of the methods provided there. This package overrides the implementation of these methods, not the semantics. The mode of operation of these routines depend on the VMS features that are controlled by the DECC features "DECC$FILENAME_REPORT_UNIX" and "DECC$EFS_CHARSET". Perl needs to be at least at 5.10 for these feature settings to work. Use of them on older perl versions on VMS will result in unpredictable operations. The default and traditional mode of these routines have been to expect VMS syntax on input and to return VMS syntax on output, even when Unix syntax was given on input. The default and traditional mode is also incompatible with the VMS "EFS", Extended File system character set, and with running Perl scripts under <GNV>, Gnu is not VMS, an optional Unix like runtime environment on VMS. If the "DECC$EFS_CHARSET" feature is enabled, These routines will now accept either VMS or UNIX syntax. If the input parameters are clearly VMS syntax, the return value will be in VMS syntax. If the input parameters are clearly in Unix syntax, the output will be in Unix syntax. This corresponds to the way that the VMS C library routines have always handled filenames, and what a programmer who has not specifically read this pod before would also expect. If the "DECC$FILENAME_REPORT_UNIX" feature is enabled, then if the output syntax can not be determined from the input syntax, the output syntax will be UNIX. If the feature is not enabled, VMS output will be the default. canonpath (override) Removes redundant portions of file specifications according to the syntax detected. catdir (override) Concatenates a list of file specifications, and returns the result as a directory specification. No check is made for "impossible" cases (e.g. elements other than the first being absolute filespecs). catfile (override) Concatenates a list of directory specifications with a filename specification to build a path. curdir (override) Returns a string representation of the current directory: '[]' or '.' devnull (override) Returns a string representation of the null device: '_NLA0:' or '/dev/null' rootdir (override) Returns a string representation of the root directory: 'SYS$DISK:[000000]' or '/' tmpdir (override) Returns a string representation of the first writable directory from the following list or '' if none are writable: /tmp if C<DECC$FILENAME_REPORT_UNIX> is enabled. sys$scratch: $ENV{TMPDIR} Since perl 5.8.0, if running under taint mode, and if $ENV{TMPDIR} is tainted, it is not used. updir (override) Returns a string representation of the parent directory: '[-]' or '..' case_tolerant (override) VMS file specification syntax is case-tolerant. path (override) Translate logical name DCL$PATH as a searchlist, rather than trying to "split" string value of $ENV{'PATH'}. file_name_is_absolute (override) Checks for VMS directory spec as well as Unix separators. splitpath (override) ($volume,$directories,$file) = File::Spec->splitpath( $path ); ($volume,$directories,$file) = File::Spec->splitpath( $path, $no_file ); Passing a true value for $no_file indicates that the path being split only contains directory components, even on systems where you can usually (when not supporting a foreign syntax) tell the difference between directories and files at a glance. splitdir (override) Split a directory specification into the components. catpath (override) Construct a complete filespec. abs2rel (override) Attempt to convert a file specification to a relative specification. On a system with volumes, like VMS, this may not be possible. rel2abs (override) Return an absolute file specification from a relative one. COPYRIGHT
Copyright (c) 2004 by the Perl 5 Porters. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
See File::Spec and File::Spec::Unix. This package overrides the implementation of these methods, not the semantics. An explanation of VMS file specs can be found at "/h71000.www7.hp.com/doc/731FINAL/4506/4506pro_014.html#apps_locating_naming_files"" in "http:. perl v5.12.1 2010-07-01 File::Spec::VMS(3pm)
All times are GMT -4. The time now is 08:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy