From: 神田基博 <mokanda@ams.odn.ne.jp>
To: <linux-kernel@vger.kernel.org>
Cc: <mokanda@itg.hitachi.co.jp>
Subject: ls SYS1.PARMLIB or Mainframe FS from Hitachi
Date: Wed, 17 Apr 2002 20:40:08 +0900 [thread overview]
Message-ID: <000701c1e604$a1ff3800$370383d3@kanda> (raw)
Hi,
Hitachi Ltd. Japan has developed a Mainframe OS compatible
file system on Linux, and will make the source code available in GPL.
The file system is named "mainframe file system" or mffs for short
and can access disks formatted by Hitachi's VOS3 operating system
and its compatibles : )
Reading and writing a plain sequential file
(DSORG=PS RECFM=F,FB,V,VB in mainframe jargon) is possible.
Partitioned dataset members
(Do not care if it dose not make sense to you.)
can be read.
Ebcdic to ascii character code translation can be performed.
So, for example, you can cat SYS1.PARMLIB/IAASYS00.
File metadata update is still under development, so you cannot create
nor extend a file.
Mainframe file system is designed in hope to replace lengthy
file transfer batch jobs. Existing mainframe volumes can be
mounted and accessed directly from Linux running on mainframes.
Let me say again. NO FILE TRANSFERS from/to mainframes.
Hitachi has modified the disk driver code under drivers/s390/block
so that mffs can issue arbitrary disk commands such as READ TRACK.
All the source code will be available in GPL in May 2002
under http://www.hitachi.co.jp/Prod/comp/soft1/linux_m/download.html
References
[1] Hitachi's press release in Japanese language
http://www.hitachi.co.jp/New/cnews/2001/1002/index.html
[2] Nikkei Linux article in Japanese, Dec. 2001, Nikkei Business
Publications, Inc.
[3] Mainframe file system on Windows NT and AIX - Towards heterogeneous
cluster file share?, Motohiro Kanda, CMG (Computer Measurement Group) 1999
Annual Conference, in English
Hope you like it.
--
mokanda@itg.hitachi.co.jp
Motohiro Kanda Hitachi Ltd. Japan
reply other threads:[~2002-04-17 11:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000701c1e604$a1ff3800$370383d3@kanda' \
--to=mokanda@ams.odn.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mokanda@itg.hitachi.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.