- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: DCL script doubts
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2009 06:50 AM
тАО11-21-2009 06:50 AM
Re: DCL script doubts
init/queue instruction creates job queue in DCL I need an equivqlent command in unix
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2009 07:02 AM
тАО11-21-2009 07:02 AM
Re: DCL script doubts
"unix" is not a very useful description of an
OS. AIX, HP-UX, Solaris, Tru64, ... would be
more helpful.
man at
man -k queue
man queuedefs
For example:
http://docs.hp.com/en/B2355-60130/queuedefs.4.html
VMS and UNIX(like) operating systems are
different. Exact translations from one to
the other are generally not possible. You
might do better if you try to learn more
about your particular UNIX(-like) operating
system(s), and quit trying to translate the
untranslatable.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-21-2009 09:07 AM
тАО11-21-2009 09:07 AM
Re: DCL script doubts
As for Unix questions...
HP-UX forum:
http://forums11.itrc.hp.com/service/forums/familyhome.do?familyId=117
HP Linux forum:
http://forums11.itrc.hp.com/service/forums/familyhome.do?familyId=118
When posting questions, do consider not asking for a VMS feature by name; you're porting, which means you're going to be ripping out most of the OpenVMS features, and you will be replacing them with platform-specific alternatives. The Unix folks won't know the features of OpenVMS like you or the folks here do, but they will know how to answer questions like "What are the recommended unix job scheduling software packages for [platform]", or similar.
Asking Unix questions in an OpenVMS forum serves to delay your port, and (unless you happen to hit a Unix user here in the forum) may not get you the best available or the most current answer(s) for your particular Unix platform.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-22-2009 09:36 PM
тАО11-22-2009 09:36 PM
Re: DCL script doubts
$ name = f$getjpi(pid, "prcnam")
$ pgcnt = f$getjpi(pid, "ppgcnt")
$ wspeak = f$getjpi(pid, "wspeak")
$ astcur = f$getjpi(pid, "astcnt")
$ astmax = f$getjpi(pid, "astlm")
$ enqcur = f$getjpi(pid, "enqcnt")
$ enqmax = f$getjpi(pid, "enqlm")
$ pgcur = f$getjpi(pid, "pagfilcnt")
$ pgmax = f$getjpi(pid, "pgflquota")
$ filcur = f$getjpi(pid, "filcnt")
$ filmax = f$getjpi(pid, "fillm")
$ f$type(ctx)
please check the attached file also.
can anybody help me in understanding these functions and how to get same vvalues in unix/linux
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2009 03:20 AM
тАО11-23-2009 03:20 AM
Re: DCL script doubts
> "unix" is not a very useful description of an
> OS. AIX, HP-UX, Solaris, Tru64, ... would be
> more helpful.
"unix/linux" is not much more helpful.
Uh, rewrite the "unix/linux" kernel? What
makes you think that these VMS parameters
have any analogues in "unix/linux"?
> please help me
You don't seem to be paying attention.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2009 06:52 AM
тАО11-23-2009 06:52 AM
Re: DCL script doubts
http://labs.hoffmanlabs.com/node/817
The bash analogs of DCL set noverify and set noon:
http://labs.hoffmanlabs.com/node/740
General list of DCL commands to bash commands:
http://labs.hoffmanlabs.com/node/741
There are no analogs to the logical name mechanisms and services including sys$trnlnm, DEFINE command, and the f$trnlnm lexical function, though there are alternatives. That DCL code will need to be replaced.
Filename handling and filename parsing is completely different between Unix and Linux and that of OpenVMS; that code will need to be entirely replaced.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2009 09:44 AM
тАО11-23-2009 09:44 AM
Re: DCL script doubts
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-23-2009 10:00 AM
тАО11-23-2009 10:00 AM
Re: DCL script doubts
Your manager (or project leader) is best positioned to provide you with the organizational and technical guidance and resources that you are seeking here.
Certainly point your manager (or project leader) to these ITRC discussions, too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2009 06:25 AM
тАО11-24-2009 06:25 AM
Re: DCL script doubts
You should have a fair understanding of the OS's you're dealing with. The more different these are, the more important this is - as you have experienced.
Without that knowlegde, you'll keep running into issues because you have no clue on what it means.
If you look around (on openvms.org, for instance) you'll find a lot of places to egt training and gain experience - free, if you like.
If you have access to a VMS system, use HELP on that system to find out.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-24-2009 07:21 AM
тАО11-24-2009 07:21 AM
Re: DCL script doubts
I've posted a very general porting sequence here:
http://labs.hoffmanlabs.com/node/225
This is a very technical undertaking, regardless.
Most any port requires detailed knowledge of both OpenVMS and of the target Unix platform; of the source and target of the port. This knowledge might be known to one person, or it might be case where a programmer familiar with the application and with OpenVMS creates a general design and requirements specification for an engineer familiar with Unix to review and implement. That design document does not and would not and should not include references to f$trnlnm or to logical names or another such OpenVMS features, but rather contains the purpose behind those references; the requirements and not the implementation.