12-27-2019
Migrating jobs from COBOL Mainframe system to UNIX system
In a nutshell requirement is to migrate the system from mainframe environment to UNIX environment (MF cobol would be used I guess). I have not much of idea in this field. I need to do some investigation on following points -
- Ease of conversion
- Known Data compatibility issue
- Issue in performance handling large volume of data
- Any other key feature that is important
I also need to know the various database options available for this task with micro focus Cobol in Unix. Above are some criteria. we can choose others as applicable. some e.g are DB 2 U DB, SYBASE , ORACLE.
Any input in this regard will be quiet helpful. Thanks in Advance
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
Does any one of you know how to invoke the cobol jobs on mainframes?
Thanks,
Waseem (3 Replies)
Discussion started by: ahmedwaseem2000
3 Replies
2. UNIX for Dummies Questions & Answers
Hello
I am looking for advise on how to convert a windows based computer system into a UNIX based operating system.. I would like to be able to learn UNIX better than I know it and work didn't allow me to work with UNIX much.
Is there a book where I could learn how to accomplish that... (6 Replies)
Discussion started by: baksg1995
6 Replies
3. Shell Programming and Scripting
Hi Experts...
Greetings for the day..!
I just want to FTP the files to mainframe system..
my code is not working..and also i need to put the files in a particular directory in a specific naming format...
ftp -i -n ${HOST_NAME} << END_FTP
user ${USER_NAME} ${PASSWORD}
put ${FILE_NAME}... (3 Replies)
Discussion started by: spkandy
3 Replies
4. Programming
Hi,
The UNIX system call inside the COBOL program is doing
the specified command correctly.
MOVE W080-UNZIP-FILE-COMMAND TO W080-OUTPUT-COMMAND
CALL "SYSTEM" USING W080-OUTPUT-COMMAND
RETURNING W080-SYS-CALL-STATUS
BUT The problem is, the following keeps on showing on the log file... (2 Replies)
Discussion started by: joyAV
2 Replies
5. UNIX for Dummies Questions & Answers
Hi friends,
I hope you are all fine and doing well. First of all, let me say that I love Unix with passion. But I have one query in my mind that is bothering me. What should I do, Unix System Administration or Unix System Programmering. Could you please tell me the difference between the two. And... (3 Replies)
Discussion started by: gabam
3 Replies
6. Shell Programming and Scripting
Hi,
I have one job that runs daily and creates daily files. At the end I compare the today's file with previous day's file. And if today's file size is greater or equal to previous day's file, then it is ok, else I need to through error.
I have following piece of code:
typeset -i... (2 Replies)
Discussion started by: ppatra
2 Replies
7. Shell Programming and Scripting
We would be migrating UNIX file system to Linux file system.
We do have many directory and sub directories with files.
after migrating unix to linux file system , i want to make sure all the files has been copied ? What would be the best approach to validate directory ,sub-directory and file... (1 Reply)
Discussion started by: balajikalai
1 Replies
8. AIX
Hello All,
I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance.
Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies
jobs(1) General Commands Manual jobs(1)
NAME
jobs - Displays status of jobs in the current session
SYNOPSIS
jobs [-l | -p] job_id...
[Tru64 UNIX] jobs [-n] job_id...
Note
The C shell has a built-in version of the jobs command. If you are using the C shell, and want to guarantee that you are using the command
described here, you must specify the full path /usr/bin/jobs. See the csh(1) reference page for a description of the built-in command.
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
jobs: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
OPTIONS
Provides more information about each job listed. This information includes the job number, current job, process group ID, state and the
command that formed the job. Displays only the process IDs for the process group leaders of the selected jobs. [Tru64 UNIX] Displays
jobs that have stopped or exited since last notified.
By default, the jobs utility displays the status of all stopped jobs, running background jobs and all jobs whose status has changed and has
not been reported by the shell.
OPERANDS
Specifies the jobs for which the status is to be displayed. If no job_id operand is given, the status information for all jobs is dis-
played. The format of job_id is described in the Jobs section of the ksh(1) reference page.
DESCRIPTION
The jobs utility displays the status of jobs that were started in the current shell environment.
When jobs reports the termination status of a job, the shell removes its process ID from the list of those "known in the current shell exe-
cution environment". See the Jobs section of the ksh(1) reference page.
RESTRICTIONS
The jobs utility does not work as expected when it is operating in its own utility execution environment because that environment has no
applicable jobs to manipulate.
EXIT STATUS
The following exit values are returned: Successful completion. An error occurred.
ENVIRONMENT VARIABLES
The following environment variables affect the execution of jobs: Provides a default value for the internationalization variables that are
unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari-
ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value,
overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes
of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale used to
affect the format and contents of diagnostic messages written to standard error and informative messages written to standard output.
Determines the location of message catalogues for the processing of LC_MESSAGES.
SEE ALSO
Commands: bg(1), csh(1), fg(1), kill(1), ksh(1), sh(1p), wait(1)
Standards: standards(5)
jobs(1)