Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Migrating jobs from COBOL Mainframe system to UNIX system Post 303042517 by Tjsureboy4me on Friday 27th of December 2019 01:48:43 PM
Old 12-27-2019
Migrating jobs from COBOL Mainframe system to UNIX system

Thanks a lot Jim. You have said a lot in your details below. I was already thinking about Micro focus Visual Cobol Development Hub because it supports Unix and Linux including Windows. You also mentioned UNIX has a tool, dd, meant for this kind of conversion.
Is there any documentation/link or relevant posts that gives much details about how you did your conversion in 2005 for EBCDIC->ASCII - it runs on UNIX.
 

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
SMBPASSWD(4)						   File Formats and Conventions 					      SMBPASSWD(4)

NAME
smbpasswd - The Samba encrypted password file SYNOPSIS
smbpasswd DESCRIPTION
This tool is part of the samba(7) suite. smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed. This file format has been evolving with Samba and has had several different formats in the past. FILE FORMAT
The format of the smbpasswd file used by Samba 2.2 is very similar to the familiar Unix passwd(4) file. It is an ASCII file containing one line for each user. Each field ithin each line is separated from the next by a colon. Any entry beginning with '#' is ignored. The smbpasswd file contains the following information for each user: name This is the user name. It must be a name that already exists in the standard UNIX passwd file. uid This is the UNIX uid. It must match the uid field for the same user entry in the standard UNIX passwd file. If this does not match then Samba will refuse to recognize this smbpasswd file entry as being valid for a user. Lanman Password Hash This is the LANMAN hash of the user's password, encoded as 32 hex digits. The LANMAN hash is created by DES encrypting a well known string with the user's password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i.e. the password is not "salted" as the UNIX password is). If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to 32 'X' characters then the user's account is marked as disabled and the user will not be able to log onto the Samba server. WARNING !! Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as plain text equivalents and must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access. NT Password Hash This is the Windows NT hash of the user's password, encoded as 32 hex digits. The Windows NT hash is created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it. This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is not "salted" as the UNIX password is). WARNING !!. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as plain text equivalents and must NOT be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access. Account Flags This section contains flags that describe the attributes of the users account. This field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters). The contents of this field may be any of the following characters: o U - This means this is a "User" account, i.e. an ordinary user. o N - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the null passwords parameter is set in the smb.conf(4) config file. o D - This means the account is disabled and no SMB/CIFS logins will be allowed for this user. o X - This means the password does not expire. o W - This means this account is a "Workstation Trust" account. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC. Other flags may be added as the code is extended in future. The rest of this field space is filled in with spaces. For further information regarding the flags that are supported please refer to the man page for the pdbedit command. Last Change Time This field consists of the time the account was last modified. It consists of the characters 'LCT-' (standing for "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch(1970) that the last change was made. All other colon separated fields are ignored at this time. VERSION
This man page is correct for version 3.0 of the Samba suite. SEE ALSO
smbpasswd(1M), Samba(7), and the Internet RFC1321 for details on the MD4 algorithm. AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. The original Samba man pages were written by Karl Auer. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/) and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +--------------------+----------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +--------------------+----------------------+ |Availability | SUNWsmbar, SUNWsmbau | +--------------------+----------------------+ |Interface Stability | External | +--------------------+----------------------+ NOTES
Source for Samba is available on http://opensolaris.org. Samba(7) delivers the set of four SMF(5) services as can be seen from the following example: $ svcs samba wins winbind swat STATE STIME FMRI disabled Apr_21 svc:/network/samba:default disabled Apr_21 svc:/network/winbind:default disabled Apr_21 svc:/network/wins:default disabled Apr_21 svc:/network/swat:default where the services are: "samba" runs the smbd daemon managing the CIFS sessions "wins" runs the nmbd daemon enabling the browsing (WINS) "winbind" runs the winbindd daemon making the domain idmap "swat" Samba Web Administration Tool is a service providing access to browser-based Samba administration interface and on-line documentation. The service runs on software loopback network interface on port 901/tcp, i.e. opening "http://localhost:901/" in browser will access the SWAT service on local machine. Please note: SWAT uses HTTP Basic Authentication scheme where user name and passwords are sent over the network in clear text. In the SWAT case the user name is root. Transferring such sensitive data is advisable only on the software loopback network interface or over secure networks. Samba 3.0 01/19/2009 SMBPASSWD(4)
All times are GMT -4. The time now is 02:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy