Sponsored Content
Top Forums Programming Porting File from OPenVMS to AIX Unix Post 64501 by jim mcnamara on Tuesday 1st of March 2005 06:04:57 PM
Old 03-01-2005
VMS relative files are just fixed record length ASCII.

ftp the file from VMS to Unix as BIN type. You can then use dd on the unix side to make text files or whatever file format you need. Or am I missing something?
 

8 More Discussions You Might Find Interesting

1. 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

2. AIX

Porting C codes from HP-UX to AIX

Hi , Can someone help me get some support documents on the common issues/pitfalls and any other details with respect to porting the application running on C codes from HP-UX to AIX. Help will be valuable. Thanks a lot (0 Replies)
Discussion started by: Sinbad
0 Replies

3. Programming

Porting of Shell to AIX

Hi All, I would like to know of the steps needed for the implementation of a shell in AIX. This shell is written by one of our developers and is currently running in Solaris. This needs to be ported to AIX. Does any of you guys know the implementation steps to do this. If so please do let me... (5 Replies)
Discussion started by: dhanamurthy
5 Replies

4. UNIX for Advanced & Expert Users

Porting linux ftpd code to Aix

Dear All, I have already ported the linux ftpd daemon to AIX earlier. When the ftp client does a "DIR" command, I have intercepted the call to the remote machine at the server code and added my code to browse IBM Message Queue, so that the client will see the files in the IBM Message... (2 Replies)
Discussion started by: srksn
2 Replies

5. AIX

Porting to AIX from Sun Solaris

Hi, When we tried to port our Pro*C programs from sun solaris to AIX, We get following error messages: The following library is not available... This library file is required for Pro*C Object Linking and Bin creation. /usr/lib/libnsl.so.1. Can anybody help us on this ? Regards rbs100 (1 Reply)
Discussion started by: rbs100
1 Replies

6. Shell Programming and Scripting

porting shell script from Linux to AIX.

Hi, I am porting one shell script from Linux to AIX. I had .ksh file and i have changed it to .sh file for aix. on linux this script is running fine but on aix it gives me "unexpected end of file" error. Could any one suggest me what to do to port this script error free? Thanks in... (6 Replies)
Discussion started by: joy_1
6 Replies

7. AIX

porting an application on 64-bit AIX version 5

Hi all, I am facing problem in porting to 64 bit AIX especially with compiling options to compile and run under 64 bit kernel.Can any one put some light on the issue thanks in advance vishal (14 Replies)
Discussion started by: vishalzone2002
14 Replies

8. AIX

Porting from HP-UX to AIX

I am orignally a VC++ programmer, this is the my post in UNIX form. I have an existing source code, that was developed in old HP-UX system, the objective is to make it work on new AIX system. It does'nt appear that AIX has the necessary libraries or even run the application if its... (0 Replies)
Discussion started by: maverick786us
0 Replies
RK(4)							     Kernel Interfaces Manual							     RK(4)

NAME
rk - RK-11/RK03 or RK05 disk DESCRIPTION
Rk? refers to an entire disk as a single sequentially-addressed file. Its 256-word blocks are numbered 0 to 4871. Minor device numbers are drive numbers on one controller. The rk files discussed above access the disk via the system's normal buffering mechanism and may be read and written without regard to physical disk records. There is also a `raw' interface which provides for direct transmission between the disk and the user's read or write buffer. A single read or write call results in exactly one I/O operation and therefore raw I/O is considerably more efficient when many words are transmitted. The names of the raw RK files begin with rrk and end with a number which selects the same disk as the corre- sponding rk file. In raw I/O the buffer must begin on a word boundary, and counts should be a multiple of 512 bytes (a disk block). Likewise seek calls should specify a multiple of 512 bytes. FILES
/dev/rk?, /dev/rrk? BUGS
In raw I/O read and write(2) truncate file offsets to 512-byte block boundaries, and write scribbles on the tail of incomplete blocks. Thus, in programs that are likely to access raw devices, read, write and lseek(2) should always deal in 512-byte multiples. RK(4)
All times are GMT -4. The time now is 04:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy