ISE, SCEP password

Hello,
ich would like to setup a BYOD enviroment withe the ISE. An i would like to use WLAN with EAP-TLS, so i need the deployment of certificates to the WLAN clients.
All configurations examples i have seen use the Microsoft CA / SCEP. That's not my case.
My CA / SCEP Server needs a password for SCEP request - but i have no idea what the ISE is using. I thing the password is within the CSR come from the client device. But this CSR generating is initated by ISE provisioning process... so there must be a way.
regards
Karsten

Karsten,
The reason the examples are using Windows is because there is a registry setting which allows you disable the password feature for SCEP requests. I dont think this is supported in version 1.2. You may need to open a TAC request and have a feature enhancment filed.
thanks,
Tarik Admani
*Please rate helpful posts*

Similar Messages

  • ISE SCEP connection to Win2003 server unsuccessful

    I'm trying to get SCEP enrollment for BYOD on-boarding to work with a Win2k3 server, so far it keeps failing. On the ISE (1.1.1), when I enter the path to the SCEP server ('https://<W2k3_srv_name>/certsrv/mscep/mscep.dll') the connectivity test fails when hitting the "Test Connectivity" button; the error message is "Connection to SCEP server failed. Remotely Closed [id: 0x00313434]". Strangely, the settings can be saved and ISE won't complain, although the ISE user guide says that the ISE will check the connectivity anyway when saving the settings.
    In the end, the on-boarding process doesn't work and stops at the stage where the cert enrollment should take place (on various platforms).
    See the Win2k3 event log error attached.
    Any ideas or experiences?
    Thanks
    Toni

    Hi Tarik
    Thanks for your support - we've also tried with HTTP, yet without success. Meanwhile we've set up a 2008 server with SCEP running on it, with this one it seems to work fine now. I deliberately say *seems to work*, since I still can't get the on-borading process to finish successfully (see attached picture).
    It works if you use an internal client on the LAN and request a cert directly from the SCEP server via IE. But for the BYOD devices, no cretificates are being rolled out, and no error or logs neither on ISE, nor on the SCEP server nor on the client indicate what's going wrong. I can't open a TAC case since this is a PoC with an Eval license and the customer will only buy the Advanced license if they like what they see...

  • How to disable ISE CLI password expiration

    ISE version 1.1.1 patch5 running on VMware.
    I got locked out yesterday due to password expiration and had to recover the CLI "admin" password using the recovery DVD.
    How can I disable this "stupid" feature from ISE?

    There is no password expiration on the CLI. There is a default password aging set to 45 days for the GUI, you can disable this by going to Administration > Admin Access > Authentication > Password Policy > Password Lifetime.
    If you are experiencing issues with the cli account then you need to raise this issue with TAC.
    Thanks,
    Tarik Admani
    *Please rate helpful posts*

  • Recover ISE CLI Password

    can anybody can tell me how to recover a password cli of the ISE?, i have no access to the cli and the gui

    its a gud article for ISE password recovery
    http://www.packetmischief.ca/2012/01/16/resetting-admin-password-on-a-cisco-ise-appliance/
    *****Do rate helpful posts******************

  • How to define challenge password (SCEP) manually in windows 2008 Enterprise CA

    reference doc (I can't past link, so I just list doc name):
    Network Device Enrollment Service (NDES) in Active Directory Certificate Services (AD CS)
    ==
    The doc said this one-time password is random.
    We can modify Registry to change password length and valid time.
    But I can't find how to define this password manually.
    e.g.  I want to set 3 password in password list/cache : aaaaa, bbbb, cccc.
    Someone know how to does this ?   
    Thanks.

    I am a bit late to this post, but I wanted to point out that a single, static SCEP password is common in the SMB market. In order configure it:
    Configure service to function in a single-password mode by creating a REG_DWORD value UseSinglePassword and setting it to 0x1.
    Give Full Control permission to the account used to run NDES for the HKEY_LOCAL_MACHINE\Microsoft\Cryptography\MSCEP registry key. This step only required if you have installed KB959193 hotfix.
    In the IIS Manager snap-in, navigate to the SCEP application pool and in Advanced Settings set Load User Profile to true.
    If you’ve configured NDES to run under some user account, logon interactively with that user account onto the machine where NDES is installed to force creation of a user profile for that account. This is a one-time operation, the user doesn’t need to stay
    interactively logged on while NDES is running.
    After above steps are complete, the NDES will use only one password for all certificate requests. This password can be obtained in the same way as a one-time password by going to the admin page of the NDES. Administrators can deploy that password to their
    devices in an automated way.

  • ISE 1.1.3.124 secondary node not reachable after registration

    G'day All,
    I'm constantly seeing that the sync and replication status for my secondary admin/monitor node in the primary node as node not reachable. The secondary still thinks it is in standalone mode. When I run the ISE diag tool connectivity tests I am able successfully ping the devices from each other using both hostname and ip and the nslookup also works fine between both nodes. Ping and nslookups also work from different networks within the environment. The two nodes are in the same vlan on a 6500 vss pair but on different switches of the pair. I'm new to ISE so any help is greatly appreciated.
    Thanks All.
    JS
    Sent from Cisco Technical Support iPhone App

    Hi Saurav,
    Thanks for your prompt repsonse...
    I have worked through that section of the document. The registration completes successfully, I've got NTP sync on both nodes and the system time on both nodes is identical.
    I am only using the self signed certificates, but following the user guide instructions I have imported the secondary's cert into the primary node.
    Just as of about 30 minutes ago, I saw an alarm on the Secondary ISE node stating that a Slow or Stuck Replication has been detected...
    As I said in the original post, I can ping the fqdn's from each other so it appears that the DNS requirements have been satisfied.
    I've changed the admin account password, I am certain that the ISE DB passwords are correct and the same on both nodes and the timezones for both nodes is the same also....
    It looks to me that registration is fine, but the first full replication isn't completing successfully
    Thanks,
    JS

  • Getting Error while registering ISE Node

    Hi All,
    I am getting below error.
    Communication failure with the host 162.12.95.167. Please check the information for the target machine, or if the target machine is accessible and try again.                
    I am Able to ping as well from primary node
    Output of ping:
    PING 162.12.95.167 (162.12.95.167) 56(84) bytes of data.
    64 bytes from 162.12.95.167: icmp_seq=1 ttl=58 time=1.02 ms
    64 bytes from 162.12.95.167: icmp_seq=2 ttl=58 time=1.05 ms
    64 bytes from 162.12.95.167: icmp_seq=3 ttl=58 time=1.05 ms
    64 bytes from 162.12.95.167: icmp_seq=4 ttl=58 time=0.955 ms
    64 bytes from 162.12.95.167: icmp_seq=5 ttl=58 time=1.02 ms
    --- 162.12.95.167 ping statistics ---
    5 packets transmitted, 5 received, 0% packet loss, time 4000ms
    rtt min/avg/max/mdev = 0.955/1.019/1.051/0.053 ms

    Hello Sachin-
    Couple of questions:
    1. Is there a firewall between the two nodes that you are trying to cluster? If yes, then have you confirmed that all of the necessary ports and protocols are opened between them?
    2. What version of ISE are you using
    3. Can you confirm that both devices are added in DNS and that both devices can ping each other via their FQDNs
    On a side note here are the prerequisites for clustering nodes:
    • The fully qualified domain name (FQDN) of the standalone node that you are going to register, for
    example, ise1.cisco.com must be DNS-resolvable from the primary Administration ISE node.
    Otherwise, node registration will fail. You must enter the IP addresses and FQDNs of the ISE nodes
    that are part of your distributed deployment in the DNS server.
    • The primary Administration ISE node and the standalone node that you are about to register as a
    secondary node should be running the same version of Cisco ISE.
    • You must configure the Cisco ISE Admin password at the time you install the Cisco ISE. The
    previous Cisco ISE Admin default login credentials (admin/cisco) are no longer valid.
    • Use the username/password that was created during the initial Setup or the current password, if it
    was changed later.
    • The DB passwords of the primary and secondary nodes should be the same. If these passwords are
    set to be different during node installation, you can modify them using the following commands:
    – application reset-passwd ise internal-database-admin
    – application reset-passwd ise internal-database-user
    • You can alternatively create an administrator account on the node that is to be registered and use
    those credentials for registering that node. Every ISE administrator account is assigned one or more
    administrative roles. To register and configure a secondary node, you must have either the Super
    Admin or System Admin role assigned. See Cisco ISE Admin Group Roles and Responsibilities for
    more information on the various administrative roles and the privileges associated with each of
    them.
    • If you plan to register a secondary Administration ISE node for high availability, we recommend
    that you register the secondary Administration ISE node with the primary first before you register
    other Cisco ISE nodes. If Cisco ISE nodes are registered in this sequence, you do not have to restart
    the secondary ISE nodes after you promote the secondary Administration ISE node as your primary.
    • If you plan to register multiple Policy Service ISE nodes running Session services and you require
    mutual failover among those nodes, you must place the Policy Service ISE nodes in a node group.
    You must create the node group first before you register the nodes because you must select the node
    group to be used on the registration page.
    “Creating, Editing, and Deleting Node Groups”
    section on page 9-21 for more information.
    • Ensure that the Certificate Trust List (CTL) of the primary node is populated with the appropriate
    Certificate Authority (CA) certificates that can be used to validate the HTTPS certificate of the
    standalone node (that you are going to register as the secondary node).
    Thank you for rating!

  • ISE 1.1.3 en Cisco IOS SCEP

    Hi,
    I'm running Cisco ISE 1.1.3.124 and a Cisco IOS 2811 (c2800nm-spservicesk9-mz.150-1.M2.bin) which I configured the be a SCEP server.
    PKI Authentication and enrollment of a Cisco switch with this SCEP server is running well but BYOD clients enrollment via EAP-TLS (1024/2048) giving me the following error on the Cisco IOS SCEP server:
    SCEP#
    .Mar 17 15:21:59.446: Sun, 17 Mar 2013 15:21:59 GMT 10.0.0.164 /cgi-bin/pkiclient.exe ok
            Protocol = HTTP/1.1 Method = GET Query = operation=PKIOperation&message=MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgU
    AMIAGCSqGSIb3DQEHAaCAJIAEggPoMIAGCSqGSIb3DQEHA6CAMIACAQAxggEvMIIBKwIBADATMA4xDDAKBgNVBAMTA2lzZQIBA
    TANBgkqhkiG9w0BAQEFAASCAQAmbK6WZ5L6gw+uh7h4Qi53XL76QsBNcY8E6cMxWDp8hWbLvujNOylSvJLF
    .Mar 17 15:21:59.446:
    .Mar 17 15:21:59.454: CRYPTO_CS: received a SCEP request, 3652 bytes
    .Mar 17 15:21:59.454: CRYPTO_CS: read SCEP: registered and bound service SCEP_READ_DB_10  
    .Mar 17 15:21:59.482: CRYPTO_CS: scep msg type - 19
    .Mar 17 15:21:59.482: CRYPTO_CS: trans id - 9871e81c65121310b77df8b341c7c887a5392da2
    .Mar 17 15:21:59.486: CRYPTO_CS: failed to open env data
    .Mar 17 15:21:59.486: CRYPTO_CS: read SCEP: unregistered and unbound service SCEP_READ_DB_10  
    .Mar 17 15:21:59.486: CRYPTO_CS: failed to read SCEP request
    .Mar 17 15:21:59.502: Sun, 17 Mar 2013 15:21:59 GMT 10.0.0.164 /cgi-bin/pkiclient.exe ok
    SCEP#
    I'm stuck now on the message: failed to open env data. So can anyone explain what the meaning is of this message or maybe know if IOS SCEP with ISE is supported ?
    Thanks in advance.
    greetz Michel
    btw the tracelog of the switch enrollment with IOS SCEP is below:
    SCEP#
    .Mar 17 14:57:10.932: Sun, 17 Mar 2013 14:57:10 GMT 10.0.0.161 /cgi-bin/pkiclient.exe ok
            Protocol = HTTP/1.0 Method = GET Query = operation=PKIOperation&message=MIIGWgYJKoZIhvcNAQcCoIIGSzCCBkcCAQExCzAJBgUrDgMCGgUAMIIDAAYJKoZI
    hvcNAQcBoIIC8QSCAu0wggLpBgkqhkiG9w0BBwOgggLaMIIC1gIBADGBujCBtwIB
    ADAgMBsxGTAXBgNVBAMTEGNhLndlc3R3aWp6ZXIubmwCAQEwDQYJKoZIhvcNAQEB
    BQAEgYAo/LNaINm+tcgzF8V8d7d5x
    .Mar 17 14:57:10.932:
    .Mar 17 14:57:10.936: CRYPTO_CS: received a SCEP request, 2210 bytes
    .Mar 17 14:57:10.940: CRYPTO_CS: read SCEP: registered and bound service SCEP_READ_DB_1   
    .Mar 17 14:57:10.948: CRYPTO_CS: scep msg type - 19
    .Mar 17 14:57:10.948: CRYPTO_CS: trans id - 59D142A6D0F525668626A435229BAAF1
    .Mar 17 14:57:11.040: CRYPTO_CS: read SCEP: unregistered and unbound service SCEP_READ_DB_1   
    .Mar 17 14:57:11.040: CRYPTO_CS: received an enrollment request
    .Mar 17 14:57:11.040: CRYPTO_PKI: creating trustpoint clone ise1
    .Mar 17 14:57:11.040: CRYPTO_CS: checking policy for enrollment request ID=1
    .Mar 17 14:57:11.040: CRYPTO_CS: request has been authorized, transaction id=59D142A6D0F525668626A435229BAAF1
    .Mar 17 14:57:11.040: CRYPTO_CS: locking the CS
    .Mar 17 14:57:11.040: CRYPTO_CS: added CDP extension
    .Mar 17 14:57:11.044: CRYPTO_CS: added key usage extension
    .Mar 17 14:57:11.044: CRYPTO_CS: Validity: 13:57:11 UTC Mar 17 2013-13:57:11 UTC Oct 3 2013
    .Mar 17 14:57:11.128: CRYPTO_CS: writing serial number 0x2.
    .Mar 17 14:57:11.180: CRYPTO_CS: file opened: nvram:ise.ser
    .Mar 17 14:57:11.180: CRYPTO_CS: Writing 32 bytes to ser file
    .Mar 17 14:57:13.864: CRYPTO_CS: reqID=1 granted, fingerprint=2
    .Mar 17 14:57:13.864: CRYPTO_CS: unlocking the CS
    .Mar 17 14:57:13.864: CRYPTO_CS: write SCEP: registered and bound service SCEP_WRTE_DB_1   
    .Mar 17 14:57:13.984: CRYPTO_CS: write SCEP: unregistered and unbound service SCEP_WRTE_DB_1   
    .Mar 17 14:57:13.988: CRYPTO_CS: Certificate generated and sent to requestor
    .Mar 17 14:57:13.988: CRYPTO_CS: removing trustpoint clone ise1

    Michel,
    Officially supported it is not:
    http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCud86973
    Some people mentioned varios degrees of "having it working".
    In your case it's the envelope data which appears to be a problem for IOS.
    M.

  • SCEP on ISE 1.2 and Windows 2003 Server

    Hi there
    has anyone ever be able to get SCEP on ISE 1.2 working with Windows 2003 Server? I know Cisco recommends Windows 2008 Server onwards, but sometimes the server infrastructure is not yet there.
    Thanks in advance and best regards
    Dominic

    Hmm, good question that I would also like to know the answer to. All of my deployments have been either 2008 or 2012. I believe long time ago I got it working in my lab with 2003 but then my 2003 server blew up so when I re-created it I did it with 2008. However, I cannot confirm 100% and even if it was true it was not in a full production environment. So it would be nice if someone else can chime in here. 
    I did come across this though that would suggest that it is supported with some tweaks:
    http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Borderless_Networks/Unified_Access/BYOD_Design_Guide/BYOD_ISE.html
    Windows Server 2003, Microsoft SCEP (MSCEP) required a Resource Kit add-on to be installed on the same computer as the CA. In Windows Server 2008, MSCEP support has been renamed NDES and is part of the operating system. NDES may be installed on a different computer than the CA (http://technet.microsoft.com/en-us/library/cc753784%28WS.10%29.aspx).
    Thank you for rating helpful posts!

  • ISE 1.2 Guest portal user cannot change their passwords

    I have a WLC 5508(version 7.6) and a server installed  the ISE (version 1.2.1.198),Now we configured the CWA,Use guest portal as an employee and guest login url,We can use the manually create internal user and password successfully logged in, and we set up allow guest users to change password in Multi-Portal, but the user can not change the password in the guest portal ,I suspect the change password option on the Guest  Portal actually works? Can anyone tell me how to change their own username password in the guest portal ?

    Requiring Guests to Change Password
    You can allow or require guest users to change their password after their initial account credentials are created by the sponsor. If guest users change their passwords, sponsors cannot provide guests with their login credentials if they are lost. The sponsor must create a new guest account.
    You can either allow guests to change their passwords, or you can require that they do it at expiration and at first login. To require internal users using a guest portal to change their password upon their next login, choose Administration > Identity Management > Identities > Users . Select the specific internal user from the Network Access Users list and enable the change password check box.
    Before You Begin
    Create a Guest portal or modify the DefaultGuestPortal. This setting is specific to each Guest portal.
    Step 1 Choose Administration > Web Portal Management > Settings > Guest > Multi-Portal Configuration.
    Step 2 Check the Guest portal to update and click Edit .
    Step 3 Click the Operations tab.
    Step 4 Check either or both options:
    Allow guest users to change password
    Require guest users to change password at expiration and first login
    Step 5 Click Save .

  • Cisco ISE 1.2 vm cli admin password recovery

    I'm having trouble getting this to work.   I was under the impression by mounting the ISO (connect at power on) i could perform the password recovery like it states for the hardware appliance.  However, if i mount the 1.2.0.899 iso image (connect at power) I don't seen to get any options in my vm console?  At most, I have a <enter> at the very beginning that will take me to Grub or ADE boot menu...  but I don't see anything about options to change the password?  

    Make sure you are following the steps in the following link:
    http://www.cisco.com/c/en/us/td/docs/security/ise/1-2/installation_guide/ise_ig/ise_postins.html#38674
    Also, make sure that the VM Guest is set to boot from DVD/CD first before trying the HDD. 
    Thank you for rating helpful posts!

  • ISE 1.1.2.145 patch-3 and CLI password disable

    I am running ISE 1.1.2.145 patch-3 on VMWare ESXi 4.1  The ISE is running fine without any issues.
    During the initial setup of the ISE, I create an account called "admin" so that I can ssh into the ISE.  According to Cisco, the CLI password does NOT expire and does NOT lock out.  However, when I ssh into the ISE and "intentionally" entered the wrong password 5 times.  After that, I can no longer ssh or console in the ISE with the "admin" account.  The only way to fix this is to do "password recovery" with the DVD.
    I notice the same issue with ISE version 1.1.1.268 patch-5 as well.
    Is this a "known" issue with ISE or bug?

    There looks like there was a bug fixed for this issue in 1.1.1, you may need to open a tac case and see if the bug has resurfaced.
    http://www.cisco.com/en/US/docs/security/ise/1.1.1/release_notes/ise111_rn.html#wp411891
    CSCub89895
    SNMP process stops randomly due to an issue in netsnmp
    The netsnmp daemon on Cisco ISE can halt, causing any SNMP monitoring of  the Cisco ISE node to fail until the daemon is restarted. This issue  has been observed in Cisco ISE, Release 1.1.1.
    Workaround   Remove all SNMP commands and re-add them to start the daemon again or restart the ISE node.
    For more information, see: http://sourceforge.net/tracker/index.php?func=detail&aid=3400106&group_id=12694&atid=112694
    Tarik Admani
    *Please rate helpful posts*

  • Can not use previous password in ISE 1.1.2 patch-5

    this is my password-policy:
    password-policy
      lower-case-required
      upper-case-required
      digit-required
      no-username
      disable-cisco-passwords
      min-password-length 6
      password-lock-retry-count 5
    I also entered the followings:
    conf t
      password-policy
      no password-locked-enabled
      no no-previous-password
    my initial "admin" account has the password of "Checkpoint1234".  It locked me out after 5 attempts from the webUI.  Fine, I CLI into the box and reset
    the password, when I tried to reset the password for "admin" to "Checkpoint1234", it tells me that I can NOT use a previous password.
    How do I disable this option altogether?  In other words, I want to use previous password. 
    By the way, in the webUI password-policy, you have to set the "Password History" between 1 and 10.  WTF!!!
    Thanks in advance.

    Admin account for the web UI seems to be locked out. So it needs to be reset from CLI.
    An incorrect password for your administrator user ID entered enough times to disable the administrator password. The minimum and default number is five. The Cisco ISE user interface “locks you out” of the system and suspends the credentials for that administrator ID until you have an opportunity to reset the password that is associated with that administrator ID. It does not affect the CLI password for the specified administrator ID
    Step 1    Access the direct-console CLI and enter the following command:
    admin# application reset-passwd ise
    Step 2    Specify a new password that is different from the previous two passwords that were used for this administrator ID:
    Enter new password:
    Confirm new password:
    Password reset successfully
    If you only want to use the previous password, you should change the password policy first. After you have successfully reset the administrator password, the credentials become immediately active in the Cisco ISE and you can log in with the new password without having to reboot your system.
    Review the section "Password Negated Due to Administrator Lockout" at the folowing location:
    http://www.cisco.com/en/US/docs/security/ise/1.1.1/installation_guide/ise_postins.html

  • ISE 1.1 'Change password on next logon' fails on iPhone / iPad

    Hello -
    We're in the process of implementing an ISE 1.1 server for Guest Wireless Access / BYOD at our company and ran into an issue with authenticating from iPhones / iPads when the account is set with 'change password on next logon' (it's a local account created on the ISE server - not AD). It fails and displays 'unable to join network' on the iPhone. The ISE log shows a '5411: No response received in 120 seconds'. We're able to authenticate from Windows devices and are prompted to change the password during the authentication process. Has anyone else encountered this? If we uncheck the 'change password' box we can authenticate from iPhones & iPads without any issue but we need to have a way for users to set their own password.
    Thanks!
    Bill

    Hi,
    I am encountering the exact same issue in our lab environment, but with AD accounts (We would like customers to be able and connect to the dot1x network with their AD credentials, and based on machine authentication they will or will not get restricted access).
    Just to be clear: the change password functionality works perfect on laptops, but on ipad/android we just cannot connect to the dot1x (PEAP) network when the "change password on next login" checkbox is on.
    Anyone else who can shed some light on this?
    Thanks
    Tom

  • HTTP Error 403 - Forbidden on Cisco ISE and SCEP RA

    Dear Experts,
    We are in process of deploying ISE 1.2 in our environment for BYOD.
    The initial step of this process is to configure ISE as an SCEP Proxy and it requires certain configuration on the local CA. We have done all the required configurations on the local CA server.
    Now, when we try to connect ISE with the local CA using SCEP RA Profiles, it gives "HTTP Error 403 - Forbidden". The URL we are using is http://ipaddress/certsrv/mscep/mscep.dll.
    It seems that the local CA is not letting the ISE access the mscep.dll file. Now I dont understand how to allow ISE to access this file or the url. Please advise if there is any step by step process guide. Although, I have followed the ones from Cisco but it doesn't state how to give ISE the required rights for accessing mscep.dll.
    Thanks in advance.
    Jay

    Jay,
    You should use this URL:
    https://ipaddress/certsrv/mscep
    If you try to get the cert from an http address, you will get an error.  You should be using https.  Also, the mscep.dll should not be part of the URL.
    You can test this connectivity from any browser by putting that URL in the sddress bar.  You should see a page similar to this:
    Please Rate Helpful posts and mark this question as answered if, in fact, this does answer your question.  Otherwise, feel free to post follow-up questions.
    Charles Moreton

Maybe you are looking for

  • Importing to itunes (iMac) from Macbook

    Relevant hardware: desktop-iMac G5, PowerPC processor, OS 10.4.2; MacBook, 2GHz Intel processor, OS 10.4.8 Relevant software: Desktop-iTunes 7.0.2, MacBook-iTunes 7.0.2 Issue: Problem transferring music files from MacBook to iMac Description: Trying

  • Problems with my power adapter!!!!

    I just got a new adapter for my Powerbook G4 the other day because the wiring at the plug on my old one wore out. My problem is that the new adapter, when plugged into my computer, sometimes just stops working like it has been unplugged or something.

  • 2900 Series Router Shows Wrong Date in Logs

    Hello All, Router: 2911 SIP Gateway (C2900-UNIVERSALK9-M) IOS Ver: Version 15.2(4)M3 When I run the "show ntp status" command it is showing the correct date/time in with the NTP data. But when I run "show logg" the SIP messages being logged are showi

  • Information Given in Report Parameters of COPA Report

    Can any please tell what information does the Keyword "Memory Table SP" and "Screen Table B" provide which is given under the Tech Data Tab for Overview of Report Parameters? It will give some information about the data rows.What does that informatio

  • VSAM file with multiple record layouts (COBOL REDEFINES)

    Hi. We're using Tuxedo 12c to migrate a COBOL/CICS/VSAM application from MVS to Solaris/Oracle 11gR2. We have a few VSAM files with record layouts that start with a record-type field, and based on that, the remainder of the record layout varies based