Operating System - OpenVMS

Re: DCL script doubts

 

Re: DCL script doubts

how to create job queue in unix ?
init/queue instruction creates job queue in DCL I need an equivqlent command in unix
Steven Schweda
Honored Contributor

Re: DCL script doubts

> how to create job queue in unix ?

"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.
Hoff
Honored Contributor

Re: DCL script doubts

cron, launchd/launchctl, /usr/local/etc/periodic/, GNU batch, Condor or, well, most anything that a Google search or a trip through available listings including http://en.wikipedia.org/wiki/Job_scheduler might show as available on your platform.

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.

Re: DCL script doubts

thank you for the help.I am able to solve my most of the 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
Steven Schweda
Honored Contributor

Re: DCL script doubts

> [...] how to get same vvalues in unix/linux

> "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.
Hoff
Honored Contributor

Re: DCL script doubts

The vmsbackup tool; a tool that can read (but not write) BACKUP saveset on Mac OS X, Unix and Linux boxes:
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.

Re: DCL script doubts

i need to now what those functions actually return the values
Hoff
Honored Contributor

Re: DCL script doubts

Please talk to your manager or (depending on your organization) your project leader about your requirements and questions here.

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.
Willem Grooters
Honored Contributor

Re: DCL script doubts

The VERY BASIC solution for your problems is EDUCATION.
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.
Willem Grooters
OpenVMS Developer & System Manager
Hoff
Honored Contributor

Re: DCL script doubts

I am aware of very little available material on this topic area; on porting OpenVMS software to Unix platforms, and for porting code from DCL to bash.

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.