Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Migrating jobs from COBOL Mainframe system to UNIX system Post 303042523 by jgt on Friday 27th of December 2019 05:53:27 PM
Old 12-27-2019
Job migration compared to system migration, implies that there is, or will be, a common data set?
We really do not have enough information about the current system and the target system to be of more help.
This User Gave Thanks to jgt For This Post:
 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to invoke cobol jobs on mainframes

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

Converting a Windows system to a UNIX system

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

FTP files to target Mainframe system

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

UNIX system call in COBOL

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

Unix System Programmer Vs. Unix System Administrator

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

Typeset -i in MVS (Mainframe system)

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

UNIX file system to Linux file system migration

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

Cloning a system via mksysb backup from one system and restore to new system

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
DH_STRIP(1)							     Debhelper							       DH_STRIP(1)

NAME
dh_strip - strip executables, shared libraries, and some static libraries SYNOPSIS
dh_strip [debhelperoptions] [-Xitem] [--dbg-package=package] [--keep-debug] DESCRIPTION
dh_strip is a debhelper program that is responsible for stripping executables, shared libraries, and static libraries that are not used for debugging. This program examines your package build directories and works out what to strip on its own. It uses file(1) and file permissions and filenames to figure out what files are shared libraries (*.so), executable binaries, and static (lib*.a) and debugging libraries (lib*_g.a, debug/*.so), and strips each as much as is possible. (Which is not at all for debugging libraries.) In general it seems to make very good guesses, and will do the right thing in almost all cases. Since it is very hard to automatically guess if a file is a module, and hard to determine how to strip a module, dh_strip does not currently deal with stripping binary modules such as .o files. OPTIONS
-Xitem, --exclude=item Exclude files that contain item anywhere in their filename from being stripped. You may use this option multiple times to build up a list of things to exclude. --dbg-package=package This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual --dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option. Causes dh_strip to save debug symbols stripped from the packages it acts on as independent files in the package build directory of the specified debugging package. For example, if your packages are libfoo and foo and you want to include a foo-dbg package with debugging symbols, use dh_strip --dbg-package=foo-dbg. This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym or --dbgsym-migration. -k, --keep-debug This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual --dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option. Debug symbols will be retained, but split into an independent file in usr/lib/debug/ in the package build directory. --dbg-package is easier to use than this option, but this option is more flexible. This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym. --dbgsym-migration=package-relation This option is used to migrate from a manual "-dbg" package (created with --dbg-package) to an automatic generated debug symbol package. This option should describe a valid Replaces- and Breaks-relation, which will be added to the debug symbol package to avoid file conflicts with the (now obsolete) -dbg package. This option implies --automatic-dbgsym and cannot be used with --keep-debug, --dbg-package or --no-automatic-dbgsym. Examples: dh_strip --dbgsym-migration='libfoo-dbg (<< 2.1-3~)' dh_strip --dbgsym-migration='libfoo-tools-dbg (<< 2.1-3~), libfoo2-dbg (<< 2.1-3~)' --automatic-dbgsym, --no-automatic-dbgsym Control whether dh_strip should be creating debug symbol packages when possible. The default is to create debug symbol packages. --ddebs, --no-ddebs Historical name for --automatic-dbgsym and --no-automatic-dbgsym. --ddeb-migration=package-relation Historical name for --dbgsym-migration. NOTES
If the DEB_BUILD_OPTIONS environment variable contains nostrip, nothing will be stripped, in accordance with Debian policy (section 10.1 "Binaries"). This will also inhibit the automatic creation of debug symbol packages. The automatic creation of debug symbol packages can also be prevented by adding noautodbgsym to the DEB_BUILD_OPTIONS environment variable. However, dh_strip will still add debuglinks to ELF binaries when this flag is set. This is to ensure that the regular deb package will be identical with and without this flag (assuming it is otherwise "bit-for-bit" reproducible). CONFORMS TO
Debian policy, version 3.0.1 SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHOR
Joey Hess <joeyh@debian.org> 11.1.6ubuntu2 2018-05-10 DH_STRIP(1)
All times are GMT -4. The time now is 07:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy